On Wed, Feb 11, 2004 at 11:43:49AM -0600, Jeff Holt wrote: > It's an excellent idea for the DBI to fake certain things when it makes > sense. But transaction control is not one of them. Transaction control > is appropriately handled only by an application. In other words, only an > application knows when it should or should not commit or rollback. > > Additionally, an application is irresponsible if it doesn't explicitly > disconnect from a session/service.
An application must take control over its transactions, to be sure, but once all transactions are committed or rolled-back, the connection itself is garbage, so there's nothing wrong with letting the garbage collector handle it. > For feature-rich dbms's, there are > well documented cases of outages caused by irresponsible applications. I'm going to start using "feature-rich" like that. ;-) Andrew
