WL#3521: Validate DEFAULT values on INSERT, UPDATE, LOAD DATA, etc.
Affects: Server-5.0 — Status: Un-Assigned — Priority: Medium
MySQL should warn (or throw an error in STRICT mode) when a DEFAULT value for a column is invalid. Currently, values are simply copied on INSERT/UPDATE/etc without any checks from those provided by an .frm file. BUG#20943 is an example where this problem occurs. The problem seems to apply to DATE/DATETIME only. Comment added by Trudy Pelzer, 2006-09-26: As discussed today with Tim Smith, the bug complains about lack of 'strict mode' behaviour in versions of MySQL before 5.0. In such cases, the behaviour is not a bug, as 'strict mode' was implemented only with MySQL 5.0 and so the results shown are expected behaviour with MySQL 4.0 and 4.1. But the behaviour shown is a bug in 5.0 and so we need to investiage whether it can be fixed in 5.0 and up. If it proves to be too intrusive to fix for 5.0, then related BUG#20943 should be marked "won't fix" for 5.0, rather than "to be fixed later". -- end comment
Copyright (c) 2000, 2018, Oracle Corporation and/or its affiliates. All rights reserved.