Subject Re: [Firebird-Architect] Metadata locking policy and caching
Author Alex Peshkov
On Tuesday 05 August 2008 16:54, Alex Peshkov wrote:
> 1. Let old transactions continue using old versions.
> 2. Do not let modify any object, used in any other running request
> (transaction, prepared statement, etc.).
> 3. Kill and unwind any request, using an object we want to modify (BTW,
> ideal when related data changes are needed).
> Certainly, both 1 and 3 are easier to implement, ...

Sorry, certainly "both 2 and 3 are easier to implement" was supposed here.