[ http://issues.apache.org/jira/browse/DERBY-970?page=all ]
Knut Anders Hatlen updated DERBY-970:
-------------------------------------
Attachment: derby-970-part2-v1.diff
derby-970-part2-v1.stat
Uploaded patch derby-970-part2-v1.diff. The patch is partial and
implements the non-controversial methods only (at least, I believe
they are non-controversial).
This patch implements the following new JDBC 4 DatabaseMetaData
methods in the client driver:
- getRowIdLifetime() - returns RowIdLifetime.ROWID_UNSUPPORTED
- supportsStoredFunctionsUsingCallSyntax() - returns true
- autoCommitFailureClosesAllResultSets() - returns false
- providesQueryObjectGenerator() - returns false
Canon for jdbc4/TestDbMetaData.java is updated to reflect that the
methods are implemented on the client.
New test cases added to TestDbMetaData:
- try to execute a stored procedure using the escape syntax, and see
if the success/failure corresponds to the value returned by
supportsStoredFunctionsUsingCallSyntax()
- open a holdable result set in auto-commit mode and, on the same
connection, execute a query which causes SQLException. Check
whether the result set is open or closed, and see if the state
corresponds to the value returned by
autoCommitFailureClosesAllResultSets()
Both derbyall and the jdbc4 suite ran successfully. Please
review. Thanks.
> Add new metadata methods to network client driver
> -------------------------------------------------
>
> Key: DERBY-970
> URL: http://issues.apache.org/jira/browse/DERBY-970
> Project: Derby
> Type: Sub-task
> Reporter: David Van Couvering
> Assignee: Knut Anders Hatlen
> Attachments: derby-970-part1-v1.diff, derby-970-part1-v1.stat,
> derby-970-part2-v1.diff, derby-970-part2-v1.stat
>
> Implement new JDBC 4.0 DatabaseMetaData methods in the client driver:
> - supportsStoredFunctionsUsingCallSyntax()
> - autoCommitFailureClosesAllResultSets()
> - getClientInfoProperties()
> - providesQueryObjectGenerator()
> - getSchemas()
> - getRowIdLifetime()
--
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
