Subject Re: [Firebird-Architect] NOT UPDATABLE fields
Author Ann W. Harrison
Claudio Valderrama C. wrote:
> The suggestion for UPDATES seems dangerous. Suppose a GUI and some
> sophisticated connectivity layer (examples abound). From each record shown,
> the user changes one or two fields, then the library can have a prepared
> UPDATE statement ...

Excellent point, and one that I hadn't considered. Of course it depends
somewhat on the implementation. If, for example, there's a way to get
the "updateablity" of a field easily - as one can now get the
"nullability" - then there isn't a problem. If the check is implemented
as a trigger that validates only that new.<field> = old.<field>, then
there's no problem. If, however, there is not easy way to verify the
updatability, and we have some check that actually catches and rejects
an effort to update the field, even if the value is the same,
sophisticated tools are going to fail.