Re: Using ON_ERROR_ROLLBACK functionality in JDBC
От | Mark Lewis |
---|---|
Тема | Re: Using ON_ERROR_ROLLBACK functionality in JDBC |
Дата | |
Msg-id | 1154102281.1634.576.camel@archimedes обсуждение исходный текст |
Ответ на | Re: Using ON_ERROR_ROLLBACK functionality in JDBC (Kris Jurka <books@ejurka.com>) |
Ответы |
Re: Using ON_ERROR_ROLLBACK functionality in JDBC
|
Список | pgsql-jdbc |
Does the current savepoint implementation in the driver require a separate round-trip? -- Mark Lewis On Fri, 2006-07-28 at 03:57 -0500, Kris Jurka wrote: > > On Fri, 28 Jul 2006, Koth, Christian (DWBI) wrote: > > > I would need the same functionality using JDBC. So I could continue with > > my batch insert even if one or more statements fail. Right now I'm > > committing the transaction after each insert. > > > > I have thought of the following: > > > > 1. Checking constraints before calling insert. (to slow) > > 2. Creating a user defined savepoint before each insert, > > and rolling back to this savepoint if the insert fails. (not tried yet) > > > > What would you recommend? Is it possible to set ON_ERROR_ROLLBACK for > > JDBC transactions? > > The JDBC driver does not currently support this behavior and if it did it > would implement it using 2) behind the scenes, so that's a good approach. > > Also it's not clear what you mean by a batch, but the use of savepoints > will not allow things like Statement.executeBatch() to commit parts of a > batch. It's all or nothing for these. > > Kris Jurka > > ---------------------------(end of broadcast)--------------------------- > TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly
В списке pgsql-jdbc по дате отправления: