Hello,
This may sound familiar since there was a discussion before...
I created an importing tool which allows users to load data into their
tables using a graphical interface.
The import operations occur within a transaction so that the user gets a
chance to change their mind.
After the import is finished the user is presented with a choice to
"abort", "commit" or interact with the
database. Interacting with the database allows the user to submit
queries to verify the data load.
Everything works great except that if the user makes any typos the
entire transaction is aborted,
requiring the import process to be done again.
I was under the impression that the nested transaction feature would
make this go away.
I played a little with it and it seems that the entire transaction is
aborted even if a checkpoint is
created.
Could someone please help me with this?
-Thanks,
Edwin S. Ramirez
