John Wolter wrote:
> Was just looking over the ToDo list and noticed a statement about 'never
> intending to do transactions support'. The stated reason for leaving them out
> was performance. Most products like ORACLE and IBM's DB2 have support for
> transactions, they may be slower but so what. Is it then necessary in MySQL to
> write all of your own transaction code? Has someone written the necessary
> support for transactions? I view transactions as necessary for applications
> like realtime accounting and other multiuser distributed applications. Someone
> enlighten me.
Hint, hint, hint:
Buy extended login support or join the development team, then you have a
lot of say in what gets done and how soon.