Re: BUG? res.next() == false, but psql finds tuples? - Mailing list pgsql-jdbc

From Palle Girgensohn
Subject Re: BUG? res.next() == false, but psql finds tuples?
Date
Msg-id BB67E201AD7D7BB34C75A481@rambutan.pingpong.net
Whole thread Raw
In response to Re: BUG? res.next() == false, but psql finds tuples?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG? res.next() == false, but psql finds tuples?
Re: BUG? res.next() == false, but psql finds tuples?
List pgsql-jdbc

--On fredag, april 22, 2005 11.01.32 -0400 Tom Lane <tgl@sss.pgh.pa.us>
wrote:

> Dave Cramer <pg@fastcrypt.com> writes:
>> Certainly looks like a bug, in the java version mango is not quoted so
>> pg thinks it is a column.
>
> But that's just sloppiness in the java log message.  The TCP dump shows
> clearly that the values are being sent as $n parameters.
>
> I'm wondering about misassignment of data types or something.  It's not
> clear though how that would result in no error but zero rows returned.
> What are the column data types exactly?

userid is text   (setInt())
courseid is int  (setString())

lang is text


Interesting that the int is transported as text, `38', but I guess there
are very good reasons for this (not having to duplicate code in the jdbvc
driver, different endians, etc).

There is no error in the pgsql log, just no result. The same connection is
beeing used for all queries. It is reproducable, every time, in our app.

/Palle

pgsql-jdbc by date:

Previous
From: Palle Girgensohn
Date:
Subject: Re: Threading problem
Next
From: Tom Lane
Date:
Subject: Re: BUG? res.next() == false, but psql finds tuples?