On Thu, 20 Mar 2003, Armin Waibel wrote: > > 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
Thanks Armin. On Thu, 20 Mar 2003, Christopher C Worley wrote: > Yuji Shinozaki, > > You can edit OJB.properties and set the debug level the sql related > entris equal to DEBUG. This will log the sql command generated and the > sql error. Sorry, i can not answer your second question. > > -chris worley > Thanks Chris, I was hoping for API access to the error information to handle this exceptions programmatically (or at least to pass on a human readable message). Maybe I can trace the logging back to it source and see if I can craft error reporting there by passing a message up through the Exception chain... 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]
