Hello, donjules2k!

Wednesday, October 13, 2004, 1:10:27 PM, you wrote:

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

ib_udf is nearly useless, because it have bugs and number of
useful functions is minimal. There are well known UDF libraries
named FreeUDFLib and RFUNC.

d> SQl Server etc you have shed loads of functions ready to go. With FB
d> you do but only if you register them.

it is not a problem even if you use some set of functions, not one.
Make script with needed declare external functions, and run it on
every database that needs them.

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

Any existing FAQ and documentation have description what is UDF, and where to get
some, and how to create new.

d> Would it be too difficult to pre-register these but as part of the
d> engine.

See above. I'm not using ib_udf at all. Also most IB/FB/YA users
use alternate UDF libraries, that have functions with the same names
as in ib_udf.

--
Dmitri Kouzmenko