On Tue, 01 Jun 2004 12:44:56 +0200 Ilja Booij <[EMAIL PROTECTED]> wrote:
> > We'll also have to make sure that we call commit or rollback > when returning with an error code. > > Ilja > I'm just underlining this WRT the daemons as a missing commit or rollback could lead to really bizarre behaviour with later invocations. As a safeguard, there should be a global transaction flag which is set by db_begin/commit/rollback(). This can essentially be used as a lock with appropiate checkpoints. Postgres will allow a BEGIN statement mid-transaction, although it does give a warning. I'm not sure how other dbs act, but for peace of mind this should be coded into the daemon instead of (or complement to) relying on the backend. -fr. -- Feargal Reilly, Codeshifter, Chrysalink Systems. ICQ: 109837009 | YIM: ectoraige PGP Key ID: 0xE721BBE6 (expires 06-Aug-2004) Visit http://ie.bsd.net/ - BSDs presence in Ireland
pgprY5iTZ3Wno.pgp
Description: PGP signature
