[DERBY-2610] Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Issue & fix info: Release Note Needed
• Assignee: Jorgen Loland
• Reporter: Jorgen Loland
• Created: 04/May/07 13:33
• Updated: 02/May/13 02:29
• Resolved: 05/Jun/07 09:33

Description

The DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys do not allow table name patterns. However, the SQL in metadata.properties implement these with "table like ?", thus allowing patterns. The SQL for these methods should be modified to "table=?".

Issue Links

• depends upon: DERBY-1484 Client and embedded behave differently when the table name is null in DatabaseMetaData methods
• relates to: DERBY-2758 ODBC metadata function "SQLForeignKeys" returns different results in 10.3.