pylint woes

[Chris Angelico]

On Mon, May 9, 2016 at 11:17 AM, Gregory Ewing
<greg.ewing at canterbury.ac.nz> wrote:
> Stephen Hansen wrote:
>>
>> The point is, you don't usually commit after an error happens. You
>> rollback.
>
>
> He might want to commit the ones that *did* go in.
> That's not necessarily wrong. It all depends on the
> surrounding requirements and workflow.

If that's the case, they should probably be being committed part way.
Generally, once the transaction state is in error, further operations
can't be done. (At least, that's how it is with *good* database
backends. I don't know what MySQL does.)

ChrisA