Dennis Nowak

Great. That solves the issues. Thanks for the fast response.

PostgreSQL: Export of inet and interval

This patch makes it work perfectly. Thanks.

There is still an issue when exporting data. When creating working tables in export workflow the tryMode is not activated so your patch ist bypassed.

The intention was getting the set of rows as seen in the transaction that exports the data set. I was not sure if it would be easy to realize my requirments. As solving this general issue is not that easy I will look for a solution to my specific use case. Thanks for your efforts.

The patched jar works as desired. Thanks.

PostreSQL: transactional execution

This really already helps me. Can the information be enhanced so that I can retrieve the primary keys of the row that were actually exported? The where clause does not necessarily list directly determine which rows will be exported. It would be nice to see those rows without having to parse the exported script and prior to loading the data into a database. In my use case it would be sufficient to get the primary keys of the subject table.