Hi Yuji, the ODMG-api use batch mode by default. I checked in a workaround for this problem (till problems are fixed). Get the last version of ConnectionManagerImpl from CVS (should work with 0.9.9 too)
http://cvs.apache.org/viewcvs.cgi/db-ojb/src/java/org/apache/ojb/broker/ accesslayer/ConnectionManagerImpl.java regards, Armin ----- Original Message ----- From: "Yuji Shinozaki" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Thursday, March 20, 2003 7:29 PM Subject: Detecting Constraint violations/Batch mode > > Using OJB 0.9.9 against Postgres 7.3.1, > > When I commit a odmg transaction that results in a constraint violation. > (typically foreignkey or unique constraints) I get the following > exception. > > org.odmg.TransactionAbortedException: Batch entry 0 > [Ljava.lang.Object;@89cc5e was aborted. > > Which unfortunately, is not very descriptive of the underlying problem. > I usually can only diagnose the problem by watching the postgres logs. > > Is there a way to get the underlying SQL error? > > And a tangential question question: > > Why is this referring to a "Batch Entry" even though I have > batch-mode=false in my repository-database.xml? > > yuji > ---- > Yuji Shinozaki Computer Systems Senior Engineer > [EMAIL PROTECTED] Advanced Technologies Group > (804)924-7171 Information Technology & Communication > http://www.people.virginia.edu/~ys2n University of Virginia > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
