Update base.py => base.utils.IntegrityError(*tuple(e.args)) not exists

[jmlefevrevulog]

No description provided.

[akoidan]

You missed some changes. I created and uploaded this under version 2.0.0 please check if it works.

[jmlefevrevulog]

You missed some changes. I created and uploaded this under version 2.0.0 please check if it works.

LogDB Error : e.cls:[OperationalError], e.bytes:[(1048, "Column 'foobar' cannot be null")] => Seems I should have integrityError right ?

[akoidan]

Not sure, could you please check what default engine throws?

[jmlefevrevulog]

Stack trace refer to mysql has gone away if that what you ask for

…

Le 25 janv. 2021 à 20:20, Andrew ***@***.***> a écrit :  Not sure, could you please check what default engine throws? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[akoidan]

Of course it does. I mean you expect IntegrityEror but you're getting OperationalError when you're using mysql_has_gone_away engine in settings.py. If you use standard mysql engine, does it throw the same?

[jmlefevrevulog]

I set back conf to original MySQL driver and retry it:
Error : e.cls:[IntegrityError], e.bytes:[(1048, "Column 'xxxxxxx' cannot be null")]
So it seems it should throw an integrity error and not a OperationalError

[akoidan]

Could you please pull from master and fix it?

[jmlefevrevulog]

I may have a look but don't know when ...
My test case raising the error is using django, having a required field in a model and try inserting without the required field.