Bug #5992 Views with check option: trigger trouble
| Submitted: | 8 Oct 2004 21:10 | Modified: | 22 Oct 2004 7:49 |
|---|---|---|---|
| Reporter: | Peter Gulutzan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.2-alpha-debug | OS: | Linux (SuSE 8.2) |
| Assigned to: | Oleksandr Byelkin | CPU Architecture: | Any |
[8 Oct 2004 21:10]
Peter Gulutzan
[8 Oct 2004 21:57]
MySQL Verification Team
Verified on latest BK source.
[21 Oct 2004 11:59]
Oleksandr Byelkin
I can't understand which relation this problem have to view? trigger fire after WITH CHECK OPTION check for view, when value go to underlying _table_. how VIEW can be responsible for underlying table mechanism? + create table t1 (s1 tinyint); + create trigger t1_bi before insert on t1 for each row set new.s1 = 500; + create view v1 as select * from t1 where s1 <> 127 with check option; + insert into v1 values (0); + Warnings: + Warning 1264 Out of range value adjusted for column 's1' at row 1 + select * from v1; + s1 + select * from t1; + s1 + 127 + insert into t1 values (0); + Warnings: + Warning 1264 Out of range value adjusted for column 's1' at row 1 + select * from t1; + s1 + 127 + 127 + select * from v1; + s1
[21 Oct 2004 13:43]
Oleksandr Byelkin
Ok, thank you for comment, I'll fix it
[21 Oct 2004 14:06]
Oleksandr Byelkin
ChangeSet 1.1668 04/10/21 17:05:45 bell@sanja.is.com.ua +3 -0 value should be checked after 'before' trigger work (BUG#5992)
[22 Oct 2004 7:49]
Oleksandr Byelkin
Thank you for bugreport! Bug is fixed, patch is pushed into our source repository.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.055 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.