Re: BUG? res.next() == false, but psql finds tuples?

From: Palle Girgensohn <girgen(at)pingpong(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pg(at)fastcrypt(dot)com
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: BUG? res.next() == false, but psql finds tuples?
Date: 2005-04-22 15:09:30
Message-ID: BB67E201AD7D7BB34C75A481@rambutan.pingpong.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

--On fredag, april 22, 2005 11.01.32 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:

> Dave Cramer <pg(at)fastcrypt(dot)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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2005-04-22 15:17:33 Re: BUG? res.next() == false, but psql finds tuples?
Previous Message Palle Girgensohn 2005-04-22 15:05:03 Re: Threading problem