All,

> > But, this is the question - will be == migrated from Yaffil to
> > Firebird as other Yaffil features.

Why not?

> Last time I was talking to Dmitry Emanov he told me this
> Yaffil piece is still a little bit flacky to be ported into
> Firebird safely at the moment.

I don't want to port Yaffil's built-in functions, as their implementation is
quite complex and some bugs/limitations are still there. This particular
feature is quite trivial and I see no problems porting it into v2.0. Let's
just agree on the syntax.

> My opinion is that we should not go PostgreSQL way
> introducing 50+ custom operators made of all combinations of
> =, *, ~, ^, /, |, !, -, ?, #, &, <, >, @ etc.
>
> Oracle way of adding built-in functions seems like better idea to me.
> Something like MODIFIED(A, B) returning TRUE if A differs
> from B considering null as a special value seems to look better.
> People can better read words instead of remembering 50
> non-standard symbol combinations. Note that many people come
> from C/C++ background and may start mismatching = and == in
> expressions by accident. C/C++ would give a warning in such
> cases while Firebird won't.

100% agreed with Nickolay here.


Dmitry