[ http://issues.apache.org/jira/browse/DERBY-1094?page=comments#action_12371199 ]
Dyre Tjeldvoll commented on DERBY-1094: --------------------------------------- AB> I hope I'm not discouraging you from pursuing this work--that's certainly not my intent. Absolutely not! Your comments are really helpful and very much appreciated! My frustration is directed toward these specs where one sentence can completely nullify whole paragraphs. I'm beginning to wonder when, if ever, those paragraphs that I referred to actually apply. Clearly I have more to learn. I'll try to ping Lance Anderson (JDBC spec lead) about the JDBC and ODBC version issue. About TIME and TIMESTAMP, my local SQL guru (Roy Lyseng, thanks!) has told me that 0 is a common DEFAULT precison for TIME, and that 6 is a common DEFAULT precison for TIMESTAMP. MAXIMUM precision is typically 6 for both. > 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
