CONNECT: no error on conversion 0 -> NULL with strict mode

Description

I don't know if this is really a bug, but this behavior is different from the one we rely on, with this SQL_MODE:

Both the DEFAULT 0 clause and the explicit 0 INSERT specify a value that is not supported for this data format. The strict mode is meant to prevent silent data changes. But even without strict mode, maybe a warnings is expected?

Environment

None

Assignee

Olivier Bertrand

Reporter

Federico Razzoli

Labels

None

Fix versions

Affects versions

Priority

Minor
Configure