[ http://issues.apache.org/jira/browse/DERBY-1094?page=comments#action_12371088 ]
Dyre Tjeldvoll commented on DERBY-1094: --------------------------------------- After reading the ODBC spec at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlprocedurecolumns.asp and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcdecimal_digits.asp I have come to the conclusion that neither the ODBC nor the JDBC query is correct. Based on my reading of the ODBC spec I think that RADIX/NUM_PREC_RADIX should be null for DATE, TIME and TIMESTAMP. SCALE/DECIMAL_DIGITS should be null for DATE, and a non-zero, non-negative number equal to the number of digits to the right of the the decimal point (fractional seconds) for TIME and TIMESTAMP. > 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
