Hello donjules2k,

Wednesday, October 13, 2004, 6:10:27 AM, you wrote:

> I agree with this suggestion. The problem is having to register UDF's
> with each DB. Why not register them by default and still have the
> ability to add extra ones if you like. It's just nice that with MySQL,
> SQl Server etc you have shed loads of functions ready to go. With FB
> you do but only if you register them.

> I also think it will put off new commers because if they do not know
> of the UDF and how to register them they will think that firebird
> lacks many features when it doesn't.

> Would it be too difficult to pre-register these but as part of the
> engine. That way they just appear in a DB, much like the simplesum and
> count functions?

What would be nice would be to have a UDF configuration file(or as in
Vulcan it could be part of the config file) where you can enter the
UDFs that you want to be available globally on the server. So, when a
query/SP/trigger/view references a UDF that is not declared in the
database, the server will look it up in the UDF config file, and if
it's there, then it will load the corresponding library and use the
UDF, otherwise it will generate an error of a UDF that was not found.

This would be a lot easier to use the UDFs that are distributed with
Firebird, since you don't have to declare them in the database. And
would make it a lot easier to use other UDF libraries, especially if
you want to use them in more than one database on the server.

This is just my 2 cents.

--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)