| From: | Jeremiah Jahn <jeremiah(at)cs(dot)earlham(dot)edu> |
|---|---|
| To: | postgres jdbc <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | changes to error reporting questions |
| Date: | 2003-03-11 20:06:11 |
| Message-ID: | 1047413170.17673.5.camel@bluejay.goodinassociates.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
before updating to 7.3 my sql errors used to report the actual SQL that
caused the error, this seems to no longer be the case. This can be a
slight pain to debug when there are a few hundred statements in a batch
update. I want to make sure that this is a change in the driver code and
not something I screwed up someplace. Is there someplace to get this
info if it is a change in the code?
Batch entry 47 [Ljava.lang.Object;@13ad33d was aborted.
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:105)
at com.goodinassociates.judici.importer.judici.DOXImporter.importDoc(Unknown Source)
at com.goodinassociates.judici.importer.judici.ImportServer$Client.run(Unknown Source)
--
Jeremiah Jahn <jeremiah(at)cs(dot)earlham(dot)edu>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J M Okomba | 2003-03-12 07:46:20 | Re: Problem with driver |
| Previous Message | Amit_Wadhwa | 2003-03-11 19:29:12 | Re: BAD INTEGER |