Dave,
I will look into this. I will check the jdbc spec to see what it says
should happen. Since it was my getBytes() changes that broke this, I
will take responsibility for fixing.
thanks,
--Barry
Dave Cramer wrote:
> It appears the getBytes was previously being used to return a byte array
> of any arbitrary column.
>
> Fixes for blobs seem to have broken this. The question is as Jason
> pointed out which do we fix.
>
> It doesn't seem unreasonable to be able to return a byte array for any
> arbitray column. On the other hand is this the intended use?
>
> Dave
>
> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org
> [mailto:pgsql-jdbc-owner@postgresql.org] On Behalf Of Jason Davies
> Sent: October 27, 2001 8:26 PM
> To: pgsql-jdbc@postgresql.org
> Subject: [JDBC] DatabaseMetaData.getTables()
>
>
> Hi,
>
> There seems to be a problem with DatabaseMetaData.getTables() when I do
> the following:
>
> ResultSet R=conn.getMetaData().getTables(null, null, "%", null);
>
> It throws a NullPointerException:
>
> java.lang.NullPointerException
> at
> org.postgresql.jdbc2.DatabaseMetaData.getTables(DatabaseMetaData.java:17
> 32)
> at Test.main(Test.java:66)
>
> Looking at the source, ResultSet.getBytes() is called and it returns
> null, causing this exception to be thrown. However I can use
> ResultSet.getString() without a problem. I'm using 7.1.3 at the moment.
> Does ResultSet.getBytes() need to be fixed or should getTables() be
> modified?
>
> I'd be grateful for any insights. Or you can just tell me to use the
> latest cvs version of PostgreSQL :) What is the consensus on supporting
> older versions, will you phase out old code when 7.2 comes out?
>
>
