[ http://issues.apache.org/jira/browse/DERBY-1094?page=comments#action_12370985 ]
Dyre Tjeldvoll commented on DERBY-1094: --------------------------------------- I starting to think that the proposed solution is unnecessarily complex. While working on DERBY-1093 I discovered how the JDBC metadata queries get transformed into their ODBC counter parts through ODBCMetaDataGenerator. Looking at the generated metadata.properties under the classes directory I found the query for ODBC SQLProcedureColumns which returns the same result set that is required for JDBC 4.0 getProcedureColumns, modulo column names. A simpler solution for getProcedureColumns 4.0 would be to just copy the ODBC query and make some adjustments. That way it would not be necessary to make any changes to TypeId or the GetProcedureColumns VTI. So I think I'm "deprecating" the preliminary patch (since I'm not allowed to delete it). Some related questions: I noticed that SQLProcedureColumns and getProcedureColumns (JDBC 3.0) do not agree on the value of SCALE and RADIX for columns with type DATE, TIME and TIMESTAMP: DATE: JDBC: SCALE=0, RADIX=10 ODBC: SCALE/DECIMAL_DIGITS=null, RADIX/NUM_PREC_RADIX=2 TIME: JDBC: SCALE=0, RADIX=10 ODBC: SCALE/DECIMAL_DIGITS=0, RADIX/NUM_PREC_RADIX=2 TIMESTAMP: JDBC: SCALE=6, RADIX=10 ODBC: SCALE/DECIMAL_DIGITS=6, RADIX/NUM_PREC_RADIX=2 I thought they should be the same? ---- All the discussion about metadata and upgrade made wonder: Will a modified VTI (with new columns) be available during soft upgrade? As soon as you start running the new software you should have access to the new columns of the VTI, right? > Make DatabaseMetaData.getProcedureColumns() JDBC4 compliant > ----------------------------------------------------------- > > Key: DERBY-1094 > URL: http://issues.apache.org/jira/browse/DERBY-1094 > Project: Derby > Type: Sub-task > Components: JDBC > Versions: 10.2.0.0 > Reporter: Dyre Tjeldvoll > Assignee: Dyre Tjeldvoll > Fix For: 10.2.0.0 > Attachments: derby-1094.preliminary.diff > > The result set returned by getProcedureColumns() must be extended with 7 > additional columns in JDBC 4.0; COLUMN_DEF, SQL_DATA_TYPE, SQL_DATETIME_SUB, > CHAR_OCTET_LENGTH, ORDINAL_POSITION, IS_NULLABLE and SPECIFIC_NAME. The > returned result set should be ordered by PROCEDURE_SCHEMA, PROCEDURE_NAME and > SPECIFIC_NAME -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
