Subject Ambiguous fields in version 1.5.3
Author Josef Gschwendtner

I wonder if the following behavior is a known problem?

We have a stored procedure (SP) with a query (Q1) joining two tables (T1
and T2).
At the time the SP was made (compiled) T1 did contain a field named
Field xx is one of the selected fields of Q1.

select xx, xy from t1, t2 where t1.f1 = t2.f1 into :xx, :xy

Now the problem arises:
We have been able to add a new field "xx" in table T2 without any
problem (I think adding new field "xx" in T2 should fail with an
appropriate message).

That there is a problem with this database we found out doing a
backup/restore of this database.
The restore failed because of some weird problems.
After droping all SP's and inserting them with a script we found out
about this ambiguous fields.

Is this a known problem? Are there any plans to improve this behavior?