Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 62297 invoked from network); 12 Aug 2008 12:12:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Aug 2008 12:12:57 -0000 Received: (qmail 54084 invoked by uid 500); 12 Aug 2008 12:12:55 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 53792 invoked by uid 500); 12 Aug 2008 12:12:54 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 53781 invoked by uid 99); 12 Aug 2008 12:12:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Aug 2008 05:12:54 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [131.246.120.220] (HELO mailgw1.uni-kl.de) (131.246.120.220) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Aug 2008 12:11:55 +0000 Received: from groupmail.informatik.uni-kl.de (gateway1-haerder.informatik.uni-kl.de [131.246.18.253]) by mailgw1.uni-kl.de (8.13.8/8.13.8/Debian-3) with ESMTP id m7CC8GmX003949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 12 Aug 2008 14:08:18 +0200 Received: from [192.168.18.93] (nb-stumm.informatik.uni-kl.de [192.168.18.93]) by groupmail.informatik.uni-kl.de (Postfix) with ESMTP id 2121ECA3B4 for ; Tue, 12 Aug 2008 14:08:17 +0200 (CEST) Message-ID: <48A17D30.3080808@informatik.uni-kl.de> Date: Tue, 12 Aug 2008 14:08:16 +0200 From: Boris Stumm User-Agent: Thunderbird 2.0.0.16 (X11/20080707) MIME-Version: 1.0 To: Derby Discussion Subject: Re: Invoking methods directly in query References: <489B1EB9.8040105@informatik.uni-kl.de> <489B4228.8060901@sun.com> In-Reply-To: <489B4228.8060901@sun.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello Rick, Rick Hillegas wrote: [...] > Unfortunately, the syntax used to declare those object types was not the > SQL Standard syntax for declaring abstract data types. Before Derby was > open-sourced, that non-standard syntax was removed so that Derby could > conform closely to the SQL Standard--that is an important part of > Derby's charter. The system tables and metadata queries were not > changed, however. Internally, Derby can still store objects in columns > and execute methods off those columns in queries. I see... and found some points in the code to change, but I think I first try out your advice on doing it. [...] > (2) You can write your own functions to unpack the information in the > TypeDescriptor that is stored in the columndatatype column. In a moment, > I will show you how to do this. Please bear in mind that TypeDescriptor > is not part of Derby's public API and that the following code is not > guaranteed to work in future releases of Derby. On the positive side, > TypeDescriptor has tended to evolve in upward compatible ways. > > Here is a function which extracts the type name out of a TypeDescriptor: [...] Thank you very much for this help, it will save me a lot of time :-) I hoped to avoid opening a new connection and use a new query because of performance reasons, but I guess I just give it a try and see if it is really that bad. [...] > Hope this helps, Yes, it did! Thanks a lot, Boris -- Dipl.-Inf. Boris Stumm; Department of Computer Science, University of Kaiserslautern; P.O. Box 3049, 67653 Kaiserslautern, Germany Tel.: +49 631 205 3264, Fax: -3299 http://lgis.informatik.uni-kl.de/cms/index.php?id=41