Lester Caine wrote:
Dan Scott wrote:
Right. And Wez posted this (partially in reply to Lester's almost
identical hysterics at that time) on this very list ages ago
(http://news.php.net/php.internals/14937 - Feb 14, 2005, to be exact):
BEGIN QUOTE:
Drivers are free(*) to implement driver specific methods on the PDO
and PDOStatement objects, provided they are "namespaced"
eg:
$db->mysqlDoSomething()
would be a mysql driver specific feature.
More generic attributes can be accessed or set via the
get/setAttribute methods.
(*) while they are "free" to do so, it's better to discuss the feature
first to see if it can be made into a more generic feature of PDO
itself
END QUOTE
NOTE the (*) - I'm TRYING to reopen the discussion on generic things
like transaction handling. Simply bolting driver specific solutions back
into each different driver in a different way is pointless? We have
those drivers already? The extra's are less of a problem than missing
CORE facilities :(
Ok, yes this is indeed an issue. PDO does not support nested
transactions. No other RDBMS that I am aware of supports this and for
all I know it does not work in the ibase driver either. Atleast we tried
to use it in MDB2 and never got it to work. Ask Lorenzo for details on this.
However again it does not prevent firebird specific methods for handling
nested transactions, which an abstraction layer author may then choose
to use in a firebird driver.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
