diff options
author | Bruce Momjian <bruce@momjian.us> | 2001-09-29 03:08:01 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2001-09-29 03:08:01 +0000 |
commit | 07ce9fe61dd6cb7399d76f4a9cbcbe191b988ff2 (patch) | |
tree | 0a33dd2f0fe8f0a906816003d2d9bdb8e36e5dc5 /src/backend/access/transam/clog.c | |
parent | 5b328502b52faa7493c057cc6407ef21333c069f (diff) | |
download | postgresql-07ce9fe61dd6cb7399d76f4a9cbcbe191b988ff2.tar.gz postgresql-07ce9fe61dd6cb7399d76f4a9cbcbe191b988ff2.zip |
Per the recent discussion there's been some code changes in JDBC's
DatabaseMetaData.getColumn(). I proposed a patch that would change the
number of queries to find out all columns in a table from 2 * N + 1 to 1 (N
being the number of columns reported) by using some outer joins. I also
fixed the fact that getColumns() only returned columns that had a default
defined. OTOH, I did not use to change the code required for obtaining a
column's remarks (by using col_description() for 7.2 and requested by Tom
Lane).
Finally, I have found a way to get all the column details in a single query
*and* use col_description() for 7.2 servers. A patch is attached. It
overrules Ren? Pijlman's fix for this that was committed just today, but
still used N + 1 queries (sorry Ren? ;-) )
I also fixed the return values for TABLE_CAT and TABLE_SCHEM from "" to
null, to be more standard compliant (and requested in Ren?'s mail found at
http://fts.postgresql.org/db/mw/msg.html?mid=1034253).
As always, the JDBC1 version has not been tested as I have no JDK 1.1
Jeroen van Vianen
Diffstat (limited to 'src/backend/access/transam/clog.c')
0 files changed, 0 insertions, 0 deletions