Re: BUG? res.next() == false, but psql finds tuples?
От | Palle Girgensohn |
---|---|
Тема | Re: BUG? res.next() == false, but psql finds tuples? |
Дата | |
Msg-id | 9372C30380841C2513B744CB@palle.girgensohn.se обсуждение исходный текст |
Ответ на | Re: BUG? res.next() == false, but psql finds tuples? (Dave Cramer <pg@fastcrypt.com>) |
Список | pgsql-jdbc |
--On fredag, april 22, 2005 11.23.12 -0400 Dave Cramer <pg@fastcrypt.com> wrote: > Palle, > > I presume you mixed the two up ? > > userid is text (setInt()) > courseid is int (setString()) indeed :-) /Palle > > > Dave > > Palle Girgensohn wrote: > >> >> >> --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 >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 5: Have you checked our extensive FAQ? >> >> http://www.postgresql.org/docs/faq >> >> > > -- > Dave Cramer > http://www.postgresintl.com > 519 939 0336 > ICQ#14675561 >
В списке pgsql-jdbc по дате отправления: