Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- From: Anders Hermansen <anders(at)yoyo(dot)no>
- To: "Vianen, Jeroen van" <jeroen(dot)van(dot)vianen(at)satama(dot)com>
- Cc: pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- Date: Fri, 30 Jul 2004 13:30:59 +0200
- Message-id: <20040730113059.GA22368@online.no> <text/plain>
* Vianen, Jeroen van (jeroen(dot)van(dot)vianen(at)satama(dot)com) wrote: > I am wondering whether it is possible to mimic JDK 1.4 root cause exception > handling in PBatchUpdateException so a decent stack trace can be logged. As a workaround put: hibernate.jdbc.batch_size = 0 in your hibernate.properties file. I believe this will disable Hibernate use of batching, and you will get a "nicer" stack trace. Hope this help, Anders
- References:
- PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- From: Vianen, Jeroen van
- PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- Prev by Date: PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- Next by Date: Re: Calling PGSQL Stored function thru JDBC
- Previous by thread: PostgreSQL JDBC + Hibernate lose valuable debug info if an exception is thrown
- Next by thread: [no subject]
- Indexes: