> 28.08.2011 15:52, Alex Peshkoff wrote:
>> Certainly, we can make API look like we_do_ join a new attachment to an
>> existing distributed transaction. To do so we just start new transaction
>> in API call internally (need to know TPB...) and join it with existing
>> distributed transaction.
>
> What would be the purpose of such action?
> If I started distributed transaction at 00:00 and joined an attachment to
> it at 00:15,
> I will see data in this database as they were at 00:15 instead of 00:00 as I
> would expect.
Your expectation is wrong as it is *you* who joined new attachment too
late. I mean -
you wrote the code and you have control when to start transactions and what to
expect.
2PC protocol is about *commit*, not about "distributed consistency".
Regards,
Vlad
------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
