Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 47343 invoked from network); 19 Apr 2006 17:03:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Apr 2006 17:03:54 -0000 Received: (qmail 70029 invoked by uid 500); 19 Apr 2006 17:03:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 69995 invoked by uid 500); 19 Apr 2006 17:03:53 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 69986 invoked by uid 99); 19 Apr 2006 17:03:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Apr 2006 10:03:53 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Apr 2006 10:03:52 -0700 Received: from brutus (localhost.localdomain [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 054407142D5 for ; Wed, 19 Apr 2006 17:02:52 +0000 (GMT) Message-ID: <21852596.1145466172016.JavaMail.jira@brutus> Date: Wed, 19 Apr 2006 17:02:52 +0000 (GMT+00:00) From: "Dyre Tjeldvoll (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (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 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-925?page=all ] Dyre Tjeldvoll updated DERBY-925: --------------------------------- Derby Info: [Patch Available] Patch is available. Some comments about the patch: A lot of the earlier comments on this issue turned out not to be relevant. The query for getFunctionParameters is mostly based on the generated ODBC getProcedureColumns query, which already has all the new columns. I did however have to extend the GetProcedureColumns VTI so that the return value (parameter) is included for functions, and that the new functionParameter* constants are used for functions. > 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, derby-925.v1.diff, derby-925.v1.stat, derbyall_report.txt > > 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