db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Van Couvering (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-970) Add new metadata methods to network client driver
Date Tue, 14 Mar 2006 19:27:42 GMT
    [ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370402 ] 

David Van Couvering commented on DERBY-970:
-------------------------------------------

So, I think Kathey's answer is the right compromise between mine and Dan's.  I agree if we
*can* reuse existing queries without affecting upgrade and compatibility, let's do so.  I
think we need to make sure as part of our tests that upgrade works and we don't have any compatibility
errors when running metadata tests.  I would think running an old client against a new database
would be a good thing, as well as upgrading an old database and making sure the new metadata
queries work correctly.

David

> 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


Mime
View raw message