Re: [PDO] PDO transaction isolation level and firebird

ADOdb is not replacement for PDO and therefore it could not be adopted instead of PDO under no circumstances. ADOdb is database abstraction layer while PDO provides only consistent interface for accessing databases. > > PDO <http://www.php.net/manual/en/intro.pdo.php> provides > a data-access > abstraction layer, which means that, regardless of which database you're > using, you use the same functions to issue queries and fetch data. PDO does > not provide a database abstraction; it doesn't rewrite SQL or emulate > missing features. You should use a full-blown abstraction layer if you need > that facility. Arguing that ADOdb should be adopted instead of PDO simply does not stand not because PDO is better then ADOdb of vice versa but because it is not valid argument. You cannot argue that orange juice is better then oranges just because you need orange juice. On 14 October 2013 09:38, Vjacheslav V. Borisov <slavb18@gmail.com> wrote: > 2013/10/13 Lester Caine <lester@lsces.co.uk>: > >> 4) php scripts typcally have short life, so using parallel > >> trasnactions to single db rarely need. parallel transactions to > >> different db of course supported. this is simply different pdo > >> instances. > > > > You miss the point here. These are not parallel transactions, but ones > which > > wrap commits between TWO databases in the ONE transaction. You CAN'T do > that > > with different PDO instances. Maintaining transfers of data from live to > > historic databases ensuring that one commits before the other is dropped. > > yes, for now this is not possible > > but i'am glad that this list is not so dead. > and developers in UK are using firebird > > -- > PDO Working Group Mailing List (http://pdo.php.net) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- schkovich PHP Dojo <http://phpdojo.blogspot.com/>