Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <307355361.1142442447992.JavaMail.jira@ajax>
Date: Wed, 15 Mar 2006 17:07:27 +0000 (GMT)
From: "Dyre Tjeldvoll (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1093) Make
 DatabaseMetaData.getProcedures() JDBC4 compliant
In-Reply-To: <245123412.1141912839245.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Dyre Tjeldvoll commented on DERBY-1093:
---------------------------------------

If I don't hear otherwise I think I'll go with option 1) since I believe it has the least potential to break any ODBC stuff. And with that option it should be easy enough for someone familiar with ODBC to clean up metadata.properties later.

> Make DatabaseMetaData.getProcedures() JDBC4 compliant
> -----------------------------------------------------
>
>          Key: DERBY-1093
>          URL: http://issues.apache.org/jira/browse/DERBY-1093
>      Project: Derby
>         Type: Sub-task
>   Components: JDBC, Newcomer
>     Versions: 10.2.0.0
>     Reporter: Dyre Tjeldvoll
>     Assignee: Dyre Tjeldvoll
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> JDBC 4.0 requires that the result set returned from getProcedures must contain a new column SPECIFIC_NAME"and that the result set must be ordered by
> PROCEDURE_SCHEM, PROCEDURE_NAME and SPECIFIC_ NAME.
> The SYSALIASES table already has a column called SPECIFICNAME, so it should only be necessary to modify the query in metadata.properties.

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