Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel
| От | Dave Cramer |
|---|---|
| Тема | Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel |
| Дата | |
| Msg-id | 674F8180-BA35-4CBA-9A4E-2A8EBDE0B095@fastcrypt.com обсуждение исходный текст |
| Ответ на | Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Support for DatabaseMetadata: getCatalogName, getTableName, getColumnLabel
|
| Список | pgsql-jdbc |
I stand corrected. I'll try to find some time this week to work on some of the outstanding issues. Tom, as of which version has this been implemented ? Dave On 29-Dec-06, at 10:47 AM, Tom Lane wrote: > Dave Cramer <pg@fastcrypt.com> writes: >> The backend does not provide us with this information, so it is not >> trivial to implement( or even possible in some cases) . > > Huh? We added table oid and column number to the RowDescription > message > specifically to support those JDBC methods. You would have to > incur an > additional round trip to the server to get names from these numbers, > but it's certainly implementable ... and I thought it'd been > implemented > long ago, so I'm a bit surprised by Ken's report. > > As for getCatalogName, I think just returning the database name (which > you should still have from the connection request) would meet the > spec. > > regards, tom lane >
В списке pgsql-jdbc по дате отправления: