From: | Eilon Reshef <eilon(dot)reshef(at)gong(dot)io> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: ResultSetMetaData.getSchemaName always return an empty string |
Date: | 2016-05-13 19:12:36 |
Message-ID: | 260c0f8b4ecb2dfec6427f186a137c63@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Thanks for the quick reply!
It’d be great if this can be added. Our current plan is to cast the
ResultSetMetaData to a Pg… one and use the getBaseSchemaName, which is
obviously less than ideal. I hope that the method (getSchemaName) isn’t
used by clients too often – probably not used directly in clients’ code
(since it returns an empty string) but might be used by some frameworks…?
Thanks again.
*From:* davecramer(at)gmail(dot)com [mailto:davecramer(at)gmail(dot)com] *On Behalf Of *Dave
Cramer
*Sent:* Friday, May 13, 2016 4:11 PM
*To:* Eilon Reshef <eilon(dot)reshef(at)gong(dot)io>
*Cc:* List <pgsql-jdbc(at)postgresql(dot)org>
*Subject:* Re: [JDBC] ResultSetMetaData.getSchemaName always return an
empty string
For some reason I thought this had been addressed. One issue is that it
will be a performance regression as it has to fetch the metadata
Dave Cramer
davec(at)postgresintl(dot)com
On 13 May 2016 at 02:08, Eilon Reshef <eilon(dot)reshef(at)gong(dot)io> wrote:
But, it seems that a valid implementation exists as getBaseSchemaName (not
part of the JDBC interface) – is there a reason why the implementation is
not carried over to the standard API call, or is this considered a bug?
Thanks
Eilon
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2016-05-14 11:42:25 | JDBC driver and Postgres 9.6beta |
Previous Message | Dave Cramer | 2016-05-13 13:11:24 | Re: ResultSetMetaData.getSchemaName always return an empty string |