I am playing with zodb storages and there is some kind of 2pc support. I
dont know if I really need it
to implement my storage (for fun) zodb over sqlite but at least I was
thinking possibility to not make those temporary changes programmatic
way but to use sqlite transactions as they are.
According to ZODB storage api manual (imcomplete and hard to
understand) I should not "write data immediately" because "if tranaction
is aborted you should to be prepared to undo". Obviously easiest way to
implement this kind of behaviour is orginal transactions of DB.
If there are no 2PC in sqlite for this purpose I can implement features
I need but then I am programming logic which I'd like to get from
database. ZODB needs are quite simple but documentation sucks. My goal
is to be able to imlement as clean as possible zodb over sqlite.
Eino
[EMAIL PROTECTED] kirjoitti:
=?ISO-8859-1?Q?Eino_M=E4kitalo?= <[EMAIL PROTECTED]> wrote:
Does sqlite support two-phase commit (2PC)?
Found some hints about it only with virtual tables.
SQLite uses a 2-phase commit internally when it is
making changes to two or more ATTACHed database files.
But that is probably not what you are asking. What
is it that you really want to know?
--
D. Richard Hipp <[EMAIL PROTECTED]>
