Helen Borrie wrote:

> It *looks* as though your DB class is being too rigorous about committing - at least that is where I would want to look if it was my code. If it is imperative that this class should never commit DML changes then a "DB class" is probably too broad. You want a connection to persist until you are ready to detach it. You want a transaction to last the shortest possible time and use the least possible resources.

The one thing I have not got my head around is *IF* the PHP5 driver IS working
properly in relation to transactions. I am sure simple stuff works correctly
and I can commit and roll back as I need to, but I am not convinced that there
isn't something else going on some of the time?

It's working fine for what I'm currently using in production, but I need to
have a closer look under the hood some time ;) When the time machine project
is finished perhaps.

--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php