[MDEV-3845] Virtual Columns are always NULL is Triggers Created: 2012-11-09 Updated: 2012-11-20 Resolved: 2012-11-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 10.0.0, 5.5.28, 5.3.8, 5.2.12 |
| Fix Version/s: | 10.0.1, 5.5.28a, 5.3.10, 5.2.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Federico Razzoli | Assignee: | Igor Babaev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
Virtual columns are always NULL in Triggers. I beilive this is a bug, because documentation says: Example:
– Then I try those:
It looks that b is treated as NULL. |
| Comments |
| Comment by Elena Stepanova [ 2012-11-09 ] |
|
Igor, Also reproducible with MyISAM and InnoDB (I've changed the test case to MyISAM). The last two statements indeed attempt to insert NULL into t2.c1 and throw an error because the column is not nullable. If you remove NOT NULL clause and try SELECT * FROM t2 afterwards, all inserted values are NULL. |
| Comment by Oleksandr Byelkin [ 2012-11-13 ] |
|
OK to push |
| Comment by Igor Babaev [ 2012-11-20 ] |
|
The fix for the bug was pushed into 5.2 (rev 3187). |