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>
Cc: pg(at)fastcrypt(dot)com, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: BUG? res.next() == false, but psql finds tuples?
Date: 2005-04-22 22:03:27
Message-ID: C7ACBCB95A235485E9CD223F@palle.girgensohn.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

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

> Palle Girgensohn <girgen(at)pingpong(dot)net> writes:
>> --On fredag, april 22, 2005 11.01.32 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>> wrote:
>>> 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())
>
> The tcpdump shows that JDBC is specifying the parameter types as 1043
> (varchar) and 23 (int4). It's hard to believe that varchar versus
> text would be an issue ... but ... what happens if you do this in
> psql?
> select lang from participant
> where userid = 'mango'::varchar and course_id = 38;

mango=# select lang from participant
mango-# where userid = 'mango'::varchar and course_id = 38;
lang
------
sv
(1 row)

i.e. works as expected...

hmmm.... is there any way to use the server's prepared statements from psql?

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2005-04-22 22:08:12 Re: Threading problem
Previous Message Palle Girgensohn 2005-04-22 22:00:32 Re: BUG? res.next() == false, but psql finds tuples?