Forum Discussion
Thanks for the response, Pero.
However, this solution would cause duplicate entries getting inserted into the id column (serial column) in the table for multiple runs of the pipeline. Postgres /Copy command allows you to do this by not including such id column and specifying the names of the other columns explicitly in the copy command.
I tried the same using the Columns field in the Postgres Bulk Load snap and included the other columns explicitly and left the serial column out. But it throws errors where it still tries to load the serial id column incorrectly.
- Aravind7117 years agoNew Contributor II
You mean creating the table on the fly with snaplogic 2nd O/P and you want to create few columns on the table.
If my understanding is correct, may i know what database you are using, If you using select snap, instead try creating with a execute snap by placing the select query and give a try, Just a heads up! - chris_claydon7 years agoNew Contributor
Hi Aravind, Yes it would be much better for me to use the Execute snap rather than the Select snap but the Execute snap does not seem to have a second output with which to pass out the table structure. I’m using JDBC snaps for the select and SQL Server snaps for the insert. The underlying database is MS SQL server on both.