On Thu, 2003-10-16 at 10:51, Chris Mason wrote: > On Thu, 2003-10-16 at 10:15, Matthew T. O'Connor wrote: > > On Thu, 2003-10-16 at 09:57, Chris Mason wrote: > > > Ok, here's a patch for dbmail 1.2 cvs that implements the transaction > > > begin/commit for mysql during pipe.c:insert_messages, and the imap > > > copy/append message commands. > > > > Great, dbmail should be using transactions, why use a database if you > > don't use transactions. > > > > indexing ;-) Before dbmail can really use transactions, it need to be > able to detect if a given table/database supports them. I'm guessing > mysql has some method for this, but haven't checked.
I don't think we should play down to the lowest common denominator here. I think that if a database doesn't support transactions, or some other feature that will make dbmail better than that database shouldn't be supported. Obviously a line has to be drawn somewhere and it's open to debate, but transactions are a simple one. I know dbmail 2.0 is trying to be more database independent, but most any database you would want to use at least supports transactions mysql, postgresql, oracle, sql server.
