[MDEV-5446] Assertion `!table || (!table->read_set || bitmap_is_set(table->read_set, field_index))' fails on EXPLAIN EXTENDED with VALUES function Created: 2013-12-14 Updated: 2014-03-14 Resolved: 2014-03-14 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.3.12, 5.5.34, 10.0.6 |
| Fix Version/s: | 5.5.37, 10.0.10, 5.3.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Description |
|
Setting to minor because it's a debug assertion, constant table and a rather meaningless use of VALUES function.
|
| Comments |
| Comment by Elena Stepanova [ 2014-03-04 ] |
|
Raising the priority because it might affect other EXPLAIN EXTENDED queries, not just those with VALUES(..), and minor issues don't even get analyzed. |
| Comment by Oleksandr Byelkin [ 2014-03-13 ] |
|
In the SELECT list we see Field object which do not belong to table in refer (probably it is a copy) with wrong field_index. |
| Comment by Oleksandr Byelkin [ 2014-03-13 ] |
|
The problem is in Item_insert_value::fix_fields trick by creating null field. |
| Comment by Oleksandr Byelkin [ 2014-03-13 ] |
|
The patch send for review. |