Re: Bad Integer

Peter,

In your postgresql.conf file set the debug_print_query to true.  This
will cause all sql statements to be printed to the log file.

thanks,
--Barry


Peter T. Brown wrote:

> No I don't. Is there any logging capabilities in Postgres I could utilize to
> expose the actual SQL select, etc.?
>
> Thanks
>
> -----Original Message-----
> From: Dave Cramer [mailto:Dave@micro-automation.net]
> Sent: Monday, December 03, 2001 4:47 PM
> To: 'Peter T. Brown'; pgsql-jdbc@postgresql.org
> Subject: RE: [JDBC] Bad Integer
>
>
> Peter,
>
> It's possible that you are running into a signed/unsigned int problem do
> you know what the value of the integer in question is?
>
> Dave
>
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Peter T. Brown
> Sent: Monday, December 03, 2001 7:31 PM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] Bad Integer
>
>
> Hi--
>
> I am using Castor w/ PostgreSQL 7.1 via JDBC, and have been getting the
> below error often lately :)
>
> Can anyone help me to correct it?
>
> Thanks
>
> Bad Integer -
>         at org.postgresql.jdbc2.ResultSet.toInt(ResultSet.java:1460)
>         at org.postgresql.jdbc2.ResultSet.getInt(ResultSet.java:247)
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
>