Flavio Palumbo wrote: > I developed a little tool in Java that updates databases throught text > files. > > In this tool there is an option that allows the user accepts a defined > amount of errors and save the well formed data. > > To do this I start commitment control when the process begins > and, at the > end, if the thershold is not reached or there are no errors I > commit data, > else rollback. > > I tested this tool under MySql and Oracle and everything went > as expected. > > Unfortunately postgres seems to work in a different way, > cause if there is > just one error while the transaction is active I'm not able > to commit the > well formed data in the db, no matter if the good records > were inserted > sooner or later the error. > > Does this behavior appears right for postgres ? > > There is any way or workaround to achieve my goal ?
You use savepoints for this: http://www.postgresql.org/docs/8.3/static/tutorial-transactions.html http://www.postgresql.org/docs/current/static/sql-savepoint.html Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
