Re: Savepoints

Going the other way, in SQL, there is a single terse SQL statement for 
starting/ending transactions, and doing the thing with savepoints.  So for aside 
from maybe some consistency with legacy DBI features, why should DBI objects 
have begin/commit/rollback or methods specific to start/end savepoints at all? 
Why doesn't the user just do it in SQL like they do everything else in SQL?  Its 
not like DBI is abstracting away other SQL language details, so why should it do 
so with the transaction/savepoint managing SQL?  Unless some DBMSs support 
transactions but not with SQL?  So maybe changing nothing in DBI is actually the 
best approach concerning savepoints. -- Darren Duncan