Re: [BUGS] JDBC ResultSet.getObject() fails for type INTERVAL
At 00:01 02/02/01 -0500, [EMAIL PROTECTED] wrote: >John Lemcke ([EMAIL PROTECTED]) reports a bug with a severity of 2 >The lower the number the more severe it is. > >Short Description >JDBC ResultSet.getObject() fails for type INTERVAL > >Long Description >Trying to retrieve an INTERVAL from a ResultSet causes an exception. The >following output is from the attached example code. > >~/src/java/rules > java TestInterval >1 >string1 >TestInterval.executeQuery() : No class found for interval. >TestInterval.main : No class found for interval. >No class found for interval. This is caused because getObject() can't find the class handling Interval. Probably because there currently isn't one. When I last checked there was 45 types in 7.1 and I think the JDBC driver has about 1/2 of them mapped to either SQL or a custom class. Shouldn't take too long to implement. Peter
[BUGS] SQL-Explorer Delphi and Access 2000/97 doesn't display tables any more
Stefan Diestelmann ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description SQL-Explorer Delphi and Access 2000/97 doesn't display tables any more Long Description I use Delphi DB-Explorer to look in my LINUX Database, therefor i use ODBC 6.50 (latest release) when browsing through the tables, no table is listed. BUT Queries and my Programms work, seems that the System-Tables could not be accessed Sample Code No file was uploaded with this report
Re: [BUGS] psql & "unexpected EOF on client connection"
[EMAIL PROTECTED] writes: > I have been getting the dreaded "unexpected EOF on client > connection" in my system logs, but the surprising thing is that > it comes from psql (I think). I am executing psql > via a 'system' system call, and about 1 time out of 20 I get > the "unexpected EOF" message. Unfortunately, this > also causes the 'system' call to return an error, even though > all SQL code was executed properly. (After searching > postgresql.org I found out that the message normally > means that PGfinish wasn't called.) So it does. I didn't think there were any paths in psql that would lead to such an ungraceful exit, especially not if no SQL error occurs. > Gory details available on request. Please. For starters, what platform are you on, and which PG version? regards, tom lane
Re: [BUGS] insert char(1) type by different ways.
"And. Andruikhanov" <[EMAIL PROTECTED]> writes: > insert into ku values(1, '\000'); This cannot work as you expect, because what comes out of the parser is a string containing a single null character --- and that's fed to a datatype input routine that expects a null-terminated string. So the char(n) input routine thinks you entered just '', which it blank-pads to one character. In general the Postgres I/O routines are not friendly to embedded nulls. The char/varchar/text types could not support embedded nulls even without the I/O problem, because they depend on C library routines like strcoll(), and those routines don't support strings with embedded nulls. regards, tom lane
