RE: SQL UDF naming limitation?

Thanks for the info Kurt.

Wasn't expecting that answer.

Digger around the manual I found the section that mentions this.  One
questions I don't see an answer too: are all the numeric data types
equivalent as far as the UDF signature is concerned?

Also for the archives, I want to mention that stored procedures are even
more restrictive.  The parameter signature is composed only of the name and
number of parameters.  The parameter type doesn't come into play as it does
with UDFs.



Charles


> -----Original Message-----
> From: Kurt Goolsbee [mailto:kurt.goolsbee@xxxxxxxxxxxxx]
> Sent: Friday, June 25, 2004 3:26 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: RE: SQL UDF naming limitation?
> 
> 
> Unfortunately the OS does not differentiate between Numeric(6,0) and
> Numeric(8,0).  It considers them both to be just Numeric when 
> it builds
> parameter signature. 
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of 
> CWilt@xxxxxxxxxxxx
> Sent: Friday, June 25, 2004 12:22 PM
> To: midrange-l@xxxxxxxxxxxx
> Subject: SQL UDF naming limitation?
> 
> Having problems overloading an SQL UDF using the specific keyword:
> 
> I can create this one:
> create function CvtToDate(indte Char(6)) returns Date
> specific CvtCharMDYtoDate                                 
> 
> then this one:
> create function CvtToDate(indte Numeric(8,0)) returns Date
> specific CvtNumISOtoDate
> 
> but when I try to create this one it fails:
> create function CvtToDate(indte Numeric(6,0)) returns Date
> specific CvtNumMDYtoDate
> 
> 
> the error I get is SQL0454 - Routine CVTTODATE in DVPMELCW 
> already exists.
> 
> 
> If I change the specific name to CvtMDYnumToDate it works fine.
> 
> If I drop the CvtToDate(numeric(8,0)) it works also.
> 
> Is there some limitation to the length of the specific name used?
> 
> Thanks,
> Charles
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> --
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>