-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> I'd be interested to see how varied the syntax is between databases. I honestly don't know, but I am pretty sure most are standard, with some (DB2?) having extensions, but still supporting the same syntax. > I'd also be interested to see a proposal for an API along with some > real-world examples. No problem, I can do that. > My position is that I'm open to being persuaded, but you'll have > to put in the leg work. The best place for that at this stage is > dbi-users as I'd like you to be able to show wider support for the > proposals from the user community. That could be tough - savepoints were just recently added to PostgreSQL, and I don't know enough about the typical users of the other RDBMSs. However, all I would like at a minimum is the acceptance of $dbh->savepoint and friends as a future addition, so that the next version of DBD::Pg can use them instead of $dbh->pg_savepoint. It still seems like an extension of the begin() and rollback() methods to me. I see begin() and friends as being useful as methods because: - - It standardizes the call across different databases, avoiding any hard-coding of SQL. - - It forces the user to go through the interface, allowing easier tracking of the transaction state, and allowing better errors/warning, such as when trying to use begin() on a system that does not support it, or if not currently inside of a transaction. Savepoints would have the same advantages as above, plus the added perk of being able to push the list of savepoints into the database handle. It also may have implications for the disconnect() method. It's late. I will try and write up an API and a dbi-users proposal soon. - -- Greg Sabino Mullane [EMAIL PROTECTED] PGP Key: 0x14964AC8 200503092341 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCL9CavJuQZxSWSsgRAgCRAJ0fDia03V56yXNR+yMTvaOBolKl4QCggxyy LFvMNCPTAYzWR+9WN4+gekI= =tQpc -----END PGP SIGNATURE-----
