> On 04/02/14 15:20, Vlad Khorsun wrote:
>
>>>> Note, it have no sence for read-committed transactions (as they have
>>>> no snapshot to share\clone) and for
>>>> "consistency write" transactions (as they will conflict on relations locks
>>>> on concurrent write attempts). I.e.
>>>> it will work for "concurrency read\write" and for "consistensy read" modes
>>>> only.
>>>>
>>>> Regards,
>>>> Vlad
>>>>
>>>> PS The most tricky part here is how to pass transaction parameters and
>>>> private copy of TIP between attacments.
>>>>
>>> From Sean's letter I've understood that he needs read-only access. If
>>> we limit ourself with "consistensy read" mode only does not it seem that
>>> implementation promises to be much simpler?
>> Coud you explain - where do you see simplification ? So far, i see no
>> reason for such strong limit...
>
> I do not see a need in private copy of TIP for read-only transaction.
> Same number should be enough. What am I missing?
You missing... private copy of TIP, which is required for any isolation
mode, except of "read committed" :)
>> BTW, i didn't thought on any implementation details yet ;)
>>
>
> Let me not believe you ;)
You know ;)
No, really, i'm busy with another things, so - no investigations of subj
feature was started by me. So far :)
Regards,
Vlad
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
