Re: Is autocommit=true bad?

Net Llama! wrote:
> At any rate, are there any negative consequences to setting setting
> autocommit=true, such as performance hits (and the obvios filling up
> diskspace because of the logging)?

The greatest negative consequence will be that the code obviously isn't
doing what the programmers think it's doing. The log entry is occuring
because someone is issuing a COMMIT somewhere - obviously expecting that
they're in a transaction at that point.

Check the code, and consider turning autocommit off if it looks like you
need a transaction over more than one statement.