Subject | Re: [firebird-support] Firebird vs Postgres |
---|---|
Author | Paul Vinkenoog |
Post date | 2007-01-08T14:45:19Z |
Hi all,
now be passed as Nulls to the function, but only if the parameter is
of a referenced type. In practice, this means that only these string
functions are fixed:
ascii_char, lower, *pad, *trim, substr*
Of these, lower, *trim and substr* shouldn't be used in new code, as
we now have internal functions LOWER, TRIM and SUBSTRING.
Declarations for the "null-enhanced" functions are in ib_udf2.sql. If
you keep using the existing declarations (in ib_udf.sql), you get the
old behaviour, where Nulls are passed as empty strings.
Greetings,
Paul Vinkenoog
>> Just about every UDF that ships with FB seems to assume that NULL ==The parameter passing mechanism has been improved somewhat. Nulls can
>> 0. Round, Sign, Sin, you name it.
> What Firebird version do you use? Because in 2.0 this is fixed AFAIK.
now be passed as Nulls to the function, but only if the parameter is
of a referenced type. In practice, this means that only these string
functions are fixed:
ascii_char, lower, *pad, *trim, substr*
Of these, lower, *trim and substr* shouldn't be used in new code, as
we now have internal functions LOWER, TRIM and SUBSTRING.
Declarations for the "null-enhanced" functions are in ib_udf2.sql. If
you keep using the existing declarations (in ib_udf.sql), you get the
old behaviour, where Nulls are passed as empty strings.
Greetings,
Paul Vinkenoog