Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1176370175.1142348869601.JavaMail.jira@ajax>
Date: Tue, 14 Mar 2006 15:07:49 +0000 (GMT)
From: "Kathey Marsden (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-970) Add new metadata methods to network
 client driver
In-Reply-To: <461963406.1139866482483.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370361 ] 

Kathey Marsden commented on DERBY-970:
--------------------------------------

Dyre said I said
>Kathey: Don't touch anything in metadata.properties!
I don't think I said that.  What I was trying to say was:

1) Don't break anything that works now when you change metadata.properties.
2) Make sure upgrade/softupgrade and downgrade are tested when you change metdata.properties
3) Keep metadata.properties on the server.
4) Be careful in there.  DERBY-1107 creates a mine field which in the past has created bugs which were impossible to fix without solution of the time travel problem.
 
As for implementation:
I think adding additional columns to existing queries is fine and perhaps preferable where possible  because it avoids duplication of queries and should not impact existing applications.
I think changing the results returned  for existing columns is probably *not*  OK.
I think adding new  queries is fine too if needed.


> 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