DatabaseMetaData use of quoted/unquoted identifiers is inconsistent [JDBC231] #280
Comments
|
Commented by: @mrotteveel See comment in HSQLDB javadoc: http://www.hsqldb.org/doc/2.0/apidocs/org/hsqldb/jdbc/JDBCDatabaseMetaData.html#getTables(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String[]) |
Modified by: @mrotteveel |
|
Commented by: @mrotteveel In Jaybird 3.0 the metadata parameters will be changed to comply with the JDBC specification with regard to case sensitivity, quoting etc. We must be careful for parts of Jaybird itself that relies on the existing case insensitivity. |
Modified by: @mrotteveelassignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ] Version: Jaybird 2.2.3 [ 10510 ] Version: Jaybird 2.2.2 [ 10480 ] Version: Jaybird 2.2.1 [ 10474 ] Version: Jaybird 2.2.4 [ 10531 ] Version: Jaybird 2.2.5 [ 10582 ] Fix Version: Jaybird 3.0 [ 10440 ] |
|
Commented by: @mrotteveel Commit: 211a0be Stricter interpretation of JDBC requirements. * Patterns are used as is (case sensitive), The exception is the OO protocol which sometimes will try the uppercase variant (this might change in the future). |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
firebird-automations
added
affect-version: Jaybird 2.1.6
affect-version: Jaybird 2.2
affect-version: Jaybird 2.2.3
affect-version: Jaybird 2.2.2
affect-version: Jaybird 2.2.1
affect-version: Jaybird 2.2.4
affect-version: Jaybird 2.2.5
fix-version: Jaybird 3.0.0
resolution: fixed
priority: major
component: jdbc driver
type: improvement
labels
Submitted by: @mrotteveel
Relate to JDBC331
The various metadata methods treat quoted and unquoted identifiers in an inconsistent way. For example getTables() and getColumns() will accept (and even require) quoted identifiers and will uppercase unquoted patterns. On the other hand getIndexInfo() only accepts unquoted identifiers and first tries the table name as is, and then tries it uppercase; using an actual quoted identifier (as accepted by getTables() and getColumns()) will not be accepted.
There is more inconsistent or questionable behaviour surrounding quoted and unquoted identifiers that needs to be investigated and made consistent; for example: should metadata methods return mixed case identifiers quoted or not (and what about identifiers that are equal to reserved (key)words), should mixed case identifiers actually be quoted when passed to the metadata method etc (getTables() specifies that the pattern should conform to the way it is stored in the database: quoted identifiers are stored mixed case without quotes, unquoted identifiers are stored uppercase).
Commits: 211a0be
The text was updated successfully, but these errors were encountered: