Bug #6404 | wrong behaviour, nested updatable VIEWs, CHECK OPTION | ||
---|---|---|---|
Submitted: | 3 Nov 2004 15:39 | Modified: | 21 Jun 2005 23:28 |
Reporter: | Matthias Leich | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 5.0 | OS: | |
Assigned to: | Oleksandr Byelkin | CPU Architecture: | Any |
[3 Nov 2004 15:39]
Matthias Leich
[21 Jun 2005 19:06]
Trudy Pelzer
This is not a bug. In standard SQL, the CHECK OPTION cascades upward, not downward. That is, if view2 has no CHECK OPTION as part of its definition (as in the example here), then the conditions for any view upon which it is based have no effect on view2. If view2 has a LOCAL CHECK OPTION, then the conditions for any view upon which it is based also have no effect on view2. Only if view2 has a [CASCADED] CHECK OPTION do the conditions of view1 have any effect on data changes to view2.