Nikolaas, upsert will not be implemented in the next release because it can’t be implemented with a common workflow for all the supported SQL dialects. But it’s possible that we will implement upsert in one of the following releases.
I can’t tell for your actual case without additional details, but in the general case you will be able to implement upsert with the following workflow:
- Use the “Select matching DB rows action” to import all the rows which are present in both EasyMorph dataset and target DB table.
- Use the “Update DB table” action to update those rows
- Use the “Keep/remove matching” action to create a dataset with rows which should be inserted
- Use the “Export to DB” action to insert those rows to the target DB table.