... and not forgetting that UDFs are meant to be used for 'quick'
functions, or in Greg Deatz's own words:

"The intent of a UDF is to perform some small operation that is not
available in SQL or InterBase's stored procedure language."

Regards,
Andrew Ferguson
-- Don't steal... The government hates competition.

--- In ib-support@y..., Helen Borrie <helebor@t...> wrote:
> At 01:18 PM 05-06-02 +0000, you wrote:
> >Hi friends...
> >Can someone experienced some perfomence test
> >on UDF and SP?
> >i.e. It is better to use a complex SP or to write
> >a Delphi UDF to manipolate date for example?
> >Thanks in advance...
>
> It's not a question of "relative performance" - they have quite
distinctly
> different and non-overlapping usages. Stored procedures manipulate
data
> for and from database columns, through SQL, and can make use of
functions,
> both internal and external (UDFs). Functions (including UDFs)
*transform*
> data and can't perform SQL.
>
> heLen
>
>
> All for Open and Open for All
> Firebird Open SQL Database · http://firebirdsql.org ·
> http://users.tpg.com.au/helebor/
> _______________________________________________________