is the section “Custom SQL” of the “Export to database” action under transaction of the section “Export” ?
I have to delete all rows & export to database some tables, but if the export fails, my table is empty until the next run of the morph project. I have to keep the data on the table if the export fails.
No, it’s not under a transaction, but it’s executed on the same connection as the export workflow. So you can use it to set session settings.
As for your case, you can try to use the “When exporting a batch fails: Add new column …” mode. This way, some rows will be exported, and you will be able to filter out rows in failed batches and create some kind of a failover workflow for them.