[ http://issues.apache.org/jira/browse/DERBY-946?page=comments#action_12375385 ]
Rick Hillegas commented on DERBY-946: ------------------------------------- In addition to the new columns in getProcedures() and getProcedureColumns() (addressed by DERBY-925), this spec change clarifies the behavior of getTypeInfo(), getCrossReference(), and getColumns(). These clarifications do not create extra work for us, for the following reasons: o getTypeIno() - This clarification only affects databases which implement SQL DISTINCT and STRUCT types. Derby does not implement these. o getCrossReference() - Derby implements the specified behavior for foreign key metadata. o getColumns() - Derby implements the correct metadatga behavior for String DEFAULTs. > Miscellaneous DatabaseMetaData methods added by JDBC 4 > ------------------------------------------------------ > > Key: DERBY-946 > URL: http://issues.apache.org/jira/browse/DERBY-946 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > > As described in the JDBC4 spec, sections 7 and 3.1. > This addresses new JDBC4 methods in DatabaseMetaData not addressed by other > JIRAs, including: > o autoCommitFailureClosesAllResultSets(). > o supportsStoredFunctionsUsingCallSyntax(). > o new getSchemas() overload -- 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
