Subject RE: [Firebird-Architect] NOT UPDATABLE fields
Author Leyne, Sean
Ann,

> So, the question, as I see it, is do we need a third mechanism?

NO!

What Adriano outlined is an application requirement, not a database
requirement.

All of the pieces are (with v2.0) in place to allow a developer to
implement the not updatable/write-once functionality outlined.

The missing piece that v2.0 provides is connection or transaction
context variable which allows for variable to be shared amongst
separated triggers/SP, without needing to pass them as 'dummy' table
columns.


Sean