Include the possibilty to make use of the UPSERT function in PostgreSQL 9.5 as a feature operation in the PostgreSQL writer in FME.
This will make it possible to do an insert or an update if there is a conflict with an existing row in the table.
For more information take a look at the PostgreSQL documentation
+17I really like this idea!! In the meantime, there is at least one workaround. Here is one pattern that I've used:
'
+8Hi @aaronkoning might it be that the DatabaseJoiner not allways does a real query into the actual table? I rather would use a select count(*) as num from mytable in an SQLExecutor and after that check with a conditional value for fme_db_operation for the value of num, since that would perform for each feature arriving at the writer that a query has been done and it will be sure that an update or insert has to be done. I tried your setup, and still records were added with the same id.
Any updates on this? I would really love to delegate conflict resolution to the database through 'on conflict' statement
This feature would make it easy for me to support near real-time synchronization between two databases. The current work-around I am using is the Database Joiner which is more complicated to set up and adds unnecessary complexity.
+32Should this read 2022 instead of 2021 "UPSERT is available in PostgreSQL as of FME 2021." ?
This article suggests it's 2022
https://community.safe.com/s/article/Updating-a-PostgreSQL-Database-Using-UPSERT
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
