Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 67B8FD1FD for ; Tue, 16 Oct 2012 18:35:05 +0000 (UTC) Received: (qmail 61717 invoked by uid 500); 16 Oct 2012 18:35:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 61657 invoked by uid 500); 16 Oct 2012 18:35:03 -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 61537 invoked by uid 99); 16 Oct 2012 18:35:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2012 18:35:03 +0000 Date: Tue, 16 Oct 2012 18:35:03 +0000 (UTC) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: <33494786.52906.1350412503842.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DERBY-2927) Procedures can't return values other than ResultSets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477251#comment-13477251 ] Dag H. Wanvik commented on DERBY-2927: -------------------------------------- Hi Rick, currently I haven't opened this up, I have just made better diagnostics. Are you suggesting we support procedures with return values iff they are declared with the DERBY keyword? And that they otherwise behave as our current procedures? > Procedures can't return values other than ResultSets > ---------------------------------------------------- > > Key: DERBY-2927 > URL: https://issues.apache.org/jira/browse/DERBY-2927 > Project: Derby > Issue Type: Improvement > Components: SQL > Affects Versions: 10.2.2.0 > Environment: Java 1.4.2 > Windows XP SP 2 > Reporter: Jacques Coetzee > Labels: derby_triage10_10 > Attachments: derby-2927-diag-2.diff, derby-2927-diag-2.stat, derby-2927-diag-3.diff, derby-2927-diag-3.stat, derby-2927-diag.diff, derby-2927-diag.stat > > > First off, this is not really a bug, it's more of a restriction. > > As per the needs of my inhouse framework I need a procedure to be able to return a value other than > a ResultSet (I need a integer). The reason I need to use a procedure; is because I'm using INOUT parameters. > > When call my procedure, it needs to look like this: > > { ? = call myProcedure(?,?,?,?,?,?)} > > Where the first ? represents a status-code, ie a failure = -1, and a successfull would be 1. > All the other procedure paramters are INOUT. > > If I where to use normal scripting methods in any other DB, for instance DB2 or Oracle > then I would be able to do this. It seems that the problem has to do with using > JAVA "Stored" Procedures. > > Is it possible to either make procedures return primitive types, OR > for Functions to be able to use OUT and INOUT paramters? > > I've got High Hopes for Derby, but it's issues like this that might just > sway me to use a different DB. > > I appreciate any feedback you can give me. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira