From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Jan-Andre le Roux <janandre(at)gen5(dot)co(dot)za> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: ResultSetMetaData Implementation Patch |
Date: | 2003-11-16 16:26:33 |
Message-ID: | Pine.LNX.4.33.0311161123290.11221-200000@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 14 Nov 2003, Jan-Andre le Roux wrote:
> Jan-Andre le Roux wrote:
> > Hi
> >
> > The patch attached implements the following Result Set Meta Information
> > methods in AbstractJdbc1ResultSetMetaData:
> >
> > getTableName(...)
> > getSchemaName(...)
> > isNullable(...)
> > getColumnName(...)
> > getColumnLabel(...)
> >
After some further testing I came across a situation where this fails to
work properly. When querying the DatabaseMetaData class a ResultSet is
created in memory without it coming from the server and a real table.
ResultSetMetaData.getColumnName() should still return the correct column
name given to the Field. Attached is a test case.
Kris Jurka
Attachment | Content-Type | Size |
---|---|---|
dbmdrsmd.java | text/plain | 548 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Larry Rosenman | 2003-11-16 18:59:30 | 7.4RC2: CLASSPATH set breaks configure? |
Previous Message | Karl von Randow | 2003-11-16 02:22:26 | Re: org.postgresql.Driver not thread-safe |