Lester Caine wrote:
In addition, while the Transaction interface can be compressed into the straight jacket that PDO defines, it would be nice to commitRetaining, but that is something that can be addressed once the need to run the native driver as well as been removed.
We did discuss the topic of how to handle transactions in depth (especially in the context of firebird) but decided that we should keep the standard transaction interface as is in order to not confuse the bulk of the users.
I really like Wez approach here (maybe cause I took the same approach in MDB2):
Give a solid common denominator that is realistically achieveable and doesnt cause too much confusion to the userbase at large, while allowing every driver to add specific functionality.
It is however key to still talk things through between the driver developers because certain non portable features may still be portable across a significant subset of RDBMS.
Obviously there are some tough calls. Like the fact that transactions are not universally supported and things like last insert id. However I think that these calls have been A+ so far in this regard ..
regards, Lukas
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
