I am in the process of junit-testing an application that is using the ODMG api.
I am intentionally violating UNIQUE constraints in the junit tests for my application, and I am now trying to figure out how to handle the resultant exception: org.odmg.TransactionAbortedException: Batch entry 0 [Ljava.lang.Object;@89cc5e was aborted. Is there a way to get the underlying SQL error? Or is there some other way to detect a constraint violation? (Besides business logic). 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]
