[MDEV-18791] Wrong error upon creating Aria table with long index on BLOB Created: 2019-03-02 Updated: 2021-03-12 Resolved: 2020-02-02 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Create Table, Data types, Storage Engine - Aria |
| Affects Version/s: | 10.4 |
| Fix Version/s: | 10.4.13 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Sachin Setiya (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Description |
|
|
| Comments |
| Comment by Sachin Setiya (Inactive) [ 2019-06-02 ] |
|
http://lists.askmonty.org/pipermail/commits/2019-June/013832.html |
| Comment by Michael Widenius [ 2019-08-07 ] |
|
The suggested bug fix is wrong:
Please ensure that the patch doesn't change this: MariaDB [test]> create or replace table t1 (a varchar(251), b int generated always as (length(a)), key (b)) engine=aria; Adding an error handler is usually not the correct way to fix the issue. The correct way would be that when MariaDB decides to use a virtual hash column for unique handling, it should check if the storage engine supports indexes on virtual columns and give an error if this is not the case. |
| Comment by Sachin Setiya (Inactive) [ 2019-08-08 ] |
|
Hi monty , |
| Comment by Sergei Golubchik [ 2019-08-21 ] |
|
ok to push |