× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Rob,

I did as you suggested the first time and noticed other myUDF's under a
different name(example: myUDF00001).  I used the 'DROP SPECIFIC FUNCTION
myUDF00001' to delete them.

Thanks,

Frank





rob@xxxxxxxxx@midrange.com on 05/23/2005 04:46:32 PM

Please respond to Midrange Systems Technical Discussion
       <midrange-l@xxxxxxxxxxxx>

Sent by:    midrange-l-bounces@xxxxxxxxxxxx


To:    Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc:

Subject:    Re: Routine myUDF in *LIBL not unique.


I strongly suggest you still do the SELECT * FROM SYSFUNCS because you
still have another function out there named myUDF but it was generated
with a different "specific" name.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





fkany@xxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/23/2005 04:28 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Routine myUDF in *LIBL not unique.








Thanks Rob.  That worked.

I used 'DROP SPECIFIC myUDF' and it worked.

Frank





rob@xxxxxxxxx@midrange.com on 05/23/2005 04:21:18 PM

Please respond to Midrange Systems Technical Discussion
       <midrange-l@xxxxxxxxxxxx>

Sent by:    midrange-l-bounces@xxxxxxxxxxxx


To:    Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc:

Subject:    Re: Routine myUDF in *LIBL not unique.


Ok, here's the deal.  You ran multiple CREATE FUNCTION's.  But, you
changed the parameters - sizes or types.  And you can have multiples. This
is called "overloading".  So if you called myUDF with one set of
parameters it may run one thing, but if you call it with a different set
it will run another.
Try this to check
SELECT * FROM SYSFUNCS and see if multiples show up.  If so, one of the
fields is specific_name.  Use that in DROP SPECIFIC FUNCTION...

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





fkany@xxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/23/2005 03:18 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
MIDRANGE-L@xxxxxxxxxxxx
cc

Subject
Routine myUDF in *LIBL not unique.







I'm using the following SQL statement to delete an SQL UDF: "DROP FUNCTION
myUDF".
I get the following error message after the SQL statement executes:
"Routine myUDF in *LIBL not unique."

Does anyone know of a way to delete UDF's?

Thanks,

Frank










As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.