Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1946922820.1141696531933.JavaMail.jira@ajax>
Date: Tue, 7 Mar 2006 01:55:31 +0000 (GMT)
From: "Kathey Marsden (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-925) Implement new JDBC 4 metadata API
 getFunctionParameters()
In-Reply-To: <1554293254.1139014924168.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-925?page=comments#action_12369129 ] 

Kathey Marsden commented on DERBY-925:
--------------------------------------

I'm interested to know  the behaviour

- if Server is at 10.1 and Client is at 10.2 
- If server and client are at different jvm versions.

This I guess is a general question about JDBC 4.0.  
What combinations should work and what errors are users  going to see if it doesn't work?

It sounds like the final conclusion was that metadata.properties won't change.  If it does  in the end need to change, I am curious the behaviour for  soft upgrade and downgrade and soft upgrade again.  This was handled in old Cloudscape versions by dropping and recreating the SPS's on every version change, but I think that is no longer done in  Derby.


> Implement new JDBC 4 metadata API getFunctionParameters()
> ---------------------------------------------------------
>
>          Key: DERBY-925
>          URL: http://issues.apache.org/jira/browse/DERBY-925
>      Project: Derby
>         Type: New Feature
>   Components: JDBC
>     Versions: 10.2.0.0
>  Environment: JDK 1.6
>     Reporter: David Van Couvering
>     Assignee: Dyre Tjeldvoll
>  Attachments: TypePrinter.java
>
> I am currently implementing this to return an empty result set so at least we're compliant, but we should be able to provide real metadata here.

-- 
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