From: | "Dave Cramer" <Dave(at)micro-automation(dot)net> |
---|---|
To: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: DatabaseMetaData.getTables() |
Date: | 2001-10-28 15:56:30 |
Message-ID: | 00e901c15fc9$1c9bc3c0$8201a8c0@inspiron |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Well I think we can restore the orignal functionality of getBytes so
that it returns a byte array for other objects
As long as we preserve the functionality for bytea types, and
LargeObjects
Dave
-----Original Message-----
From: Jason Davies [mailto:jason(at)netspade(dot)com]
Sent: October 28, 2001 8:34 AM
To: Dave Cramer
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: [JDBC] DatabaseMetaData.getTables()
On Sun, Oct 28, 2001 at 07:14:42AM -0500, 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?
This is what the documentation says:
public byte[] getBytes(int columnIndex)
throws SQLException
Retrieves the value of the designated column in the current
row
of this ResultSet object as a byte array in the Java
programming language. The bytes represent the raw values
returned by the driver.
It seems to imply that it _should_ return a byte array for any arbitary
column. But as usual, it's up to us to decide. I think it's reasonable,
since we are working with byte arrays in the code anyway.
--
Jason Davies
jason(at)netspade(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Henry D. | 2001-10-28 20:14:16 | Re: JDBC SQLCodes or Error Numbers - Or how to handle errors |
Previous Message | Jason Davies | 2001-10-28 13:33:39 | Re: DatabaseMetaData.getTables() |