aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces/ecpg/lib/execute.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-08-17 13:59:29 +0000
committerBruce Momjian <bruce@momjian.us>2001-08-17 13:59:29 +0000
commit1ebbfc150a6bf3baa7ab256018b85385c3514737 (patch)
tree51f77e888c533308ec6a8bbf8a9a863a9e22ea97 /src/interfaces/ecpg/lib/execute.c
parentb5453fae742c5130086989b51498a201ef2ee086 (diff)
downloadpostgresql-1ebbfc150a6bf3baa7ab256018b85385c3514737.tar.gz
postgresql-1ebbfc150a6bf3baa7ab256018b85385c3514737.zip
Attached is the patch requested by Tom Lane (see below). It
includes two changes in the JDBC driver: 1) When connected to a backend >= 7.2: use obj_description() and col_description() instead of direct access to pg_description. 2) In DatabaseMetaData.getTables()/getColumns()/getProcedures(): when there is no comment on the object, return null in the REMARKS column of the ResultSet, instead of the default string "no remarks". Change 2 first appeared as a side-effect of change 1, but it is actually more compliant with the JDBC spec: "String object containing an explanatory comment on the table/column/procedure, which may be null". The default string "no remarks" was strictly speaking incorrect, as it could not be distinguished from a real user comment "no remarks". So I removed the default string completely. Change 2 might break existing code that doesn't follow the JDBC spec and isn't prepared to handle a null in the REMARKS column of getTables()/getColumns()/getProcedures. Patch tested with jdbc2 against both a 7.1 and a CVS tip backend. I did not have a jdbc1 environment to build and test with, but since the touched code is identical in jdbc1 and jdbc2 I don't foresee any problems. Regards, Ren? Pijlman
Diffstat (limited to 'src/interfaces/ecpg/lib/execute.c')
0 files changed, 0 insertions, 0 deletions