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.
- pmancevski3 years agoNew Contributor III
Hi @aprabhav,
For the sake of discussion 🙂 and if adding additional field resolve your issue.
If you are concern about id duplicates, you can always do a quick look up into the table and get the most recent id. After that snap.in.totalCount + look up value.For example:
param1 = 222;Result:
Thanks,
Pero M.Thanks Pero for your helpful suggestions.
It should not be required to add the serial column data in the input document.
I was able to fix this problem by doing the following…
- specified the list of columns (excluding the serial id column) in the Columns list in the snap
- used ‘Text’ option for the format field in the snap
- unchecked ‘Header provided’ field in the snap.
Related Content
- 2 years ago
- 4 years ago
- 4 years ago
- 4 years ago
- 3 years ago