db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: [PATCH]Derby-229
Date Mon, 02 May 2005 16:23:59 GMT
Bernt M. Johnsen wrote:
> Hi all,
> I have the following comment to this patch. This solves the problem of
> getting the *first* matching column instead of the *last*.
> But: Since DatabaseMetaData.supportsMixedCaseQuotedIdentifiers()
> return true (which is a requirement to JDBC compliant drivers), it
> should be possible to do e.g. getXXX("\"quotedId\"") to get the column
> which exactly matches "quotedId". (Alternatively,
> supportsMixedCaseQuotedIdentifiers() could return false, but then the
> driver would not be JDBC compliant).

The JDBC tutorial (second edition) books says for this method

 "Checks whether the database treats mixed ..."

note the *database*, not the driver. I think this method is describing
how identifiers behave in SQL statements, not in JDBC method calls.

Also section 26.1.5 of JDBC tutorial book (second edition) describes how
 duplicate column names are handled, and it says if there are identical
names the application needs to use a column index to obtain the correct
value. Nothing about quoted names in JDBC method calls.


View raw message