You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Elton Barendse - Quintessence Systems <el...@in2j.com> on 2004/10/06 10:01:13 UTC
Overloading of PROCEDUREs and FUNCTIONs
Hi,
I notice that the "Overloading of PROCEDUREs and FUNCTIONs" is a current
(but apparently unassigned) item on the Apache Derby TO-DO list.
Can anyone provide an indication of:
1) What kind of effort might be required to implement this feature i.e. An
estimate of how long we might be looking at from assignment/development to
community availability?
2) Is there any (official or unofficial) knowledge of who might pick up this
to-do...and when?
Many thanks in advance.
Elton
Elton Barendse
Quintessence Systems
http://www.in2j.com
elton.barendse@in2j.com
T: +44 1628 628 550
RE: Overloading of PROCEDUREs and FUNCTIONs
Posted by Elton Barendse - Quintessence Systems <el...@in2j.com>.
Thanks for your insights.
Elton
-----Original Message-----
From: Daniel John Debrunner [mailto:djd@debrunners.com]
Sent: 06 October 2004 15:33
To: Derby Development
Subject: Re: Overloading of PROCEDUREs and FUNCTIONs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Elton Barendse - Quintessence Systems wrote:
> Hi,
>
> I notice that the "Overloading of PROCEDUREs and FUNCTIONs" is a current
> (but apparently unassigned) item on the Apache Derby TO-DO list.
>
> Can anyone provide an indication of:
>
> 1) What kind of effort might be required to implement this feature i.e. An
> estimate of how long we might be looking at from assignment/development to
> community availability?
Some of the code is setup to handle overloaded routines. The additional
work needed is (at least):
- - Store any user supplied SPECIFIC NAME from the create in the
SYSALIASES table. Currently a system generated name is always used.
- - Support DROP SPECIFIC PROCEDURE/FUNCTION
- - Ensure indexes on SYSALIASES are set up to allow multiple routines
with the same name. I think they are correct.
- - Ensure routine resolution is correct at runtime. The resolution code
currently does get a list of routines back from the data dictionary, but
that list only ever has zero or one entry. Resolution rules I presume
are defined in the SQL standard.
- - upgrade work before functionality can be part of a release.
These are all fairly independent tasks.
> 2) Is there any (official or unofficial) knowledge of who might pick
up this
> to-do...and when?
I don't know of anyone actively working on this.
It would be a good introduction project(s) to the Derby language code.
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBZAInIv0S4qsbfuQRAv5oAJ4vtCzuTRmdDODecXBJueG19P+vXgCg0ZMi
2M6E832mmoDaGI9gNHtmbNQ=
=2gmv
-----END PGP SIGNATURE-----
Re: Overloading of PROCEDUREs and FUNCTIONs
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Elton Barendse - Quintessence Systems wrote:
> Hi,
>
> I notice that the "Overloading of PROCEDUREs and FUNCTIONs" is a current
> (but apparently unassigned) item on the Apache Derby TO-DO list.
>
> Can anyone provide an indication of:
>
> 1) What kind of effort might be required to implement this feature i.e. An
> estimate of how long we might be looking at from assignment/development to
> community availability?
Some of the code is setup to handle overloaded routines. The additional
work needed is (at least):
- - Store any user supplied SPECIFIC NAME from the create in the
SYSALIASES table. Currently a system generated name is always used.
- - Support DROP SPECIFIC PROCEDURE/FUNCTION
- - Ensure indexes on SYSALIASES are set up to allow multiple routines
with the same name. I think they are correct.
- - Ensure routine resolution is correct at runtime. The resolution code
currently does get a list of routines back from the data dictionary, but
that list only ever has zero or one entry. Resolution rules I presume
are defined in the SQL standard.
- - upgrade work before functionality can be part of a release.
These are all fairly independent tasks.
> 2) Is there any (official or unofficial) knowledge of who might pick
up this
> to-do...and when?
I don't know of anyone actively working on this.
It would be a good introduction project(s) to the Derby language code.
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBZAInIv0S4qsbfuQRAv5oAJ4vtCzuTRmdDODecXBJueG19P+vXgCg0ZMi
2M6E832mmoDaGI9gNHtmbNQ=
=2gmv
-----END PGP SIGNATURE-----