[MDEV-9045] Inconsistent handling of "ALGORITHM=INPLACE" with PERSISTENT generated columns. Created: 2015-10-30  Updated: 2016-02-15  Resolved: 2016-02-15

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table, Virtual Columns
Affects Version/s: 10.0.22, 10.1.8
Fix Version/s: 10.0.24, 10.1.12

Type: Bug Priority: Major
Reporter: Jiri Kavalik Assignee: Sergei Golubchik
Resolution: Fixed Votes: 1
Labels: None
Environment:

Ubuntu 12.04 64bit

Attachments: File inplace_results_10_0_22.sql     File inplace_test.sql    
Sprint: 10.0.24

 Description   

It is not possible to add a PERSISTENT virtual column using ALGORITHM=INPLACE but it is possible to drop it (together with an index on it) that way.

And while the column is present in the table, it is not possible to add/drop any index using ALGORITHM=INPLACE (so if I understand it, "fast index creation" is not available).

alter ONLINE table ... behaves the same.

Thanks to danblack for extending the testcase and testing on 10.1.8 http://pastie.org/10517538

 Comments   
Comment by Sergei Golubchik [ 2016-02-10 ]

I've relaxed the restriction, but didn't remove it completely.

In 10.0.24

  • one will be able to add or drop indexes inplace even if the table have persistent generated columns
  • one will be able to drop or add columns inplace even if the table have persistent generated columns
  • adding a persistent generated column still cannot be done inplace, because inplace alter is done internally inside the engine, and only the sql layer can evaluate the expression to generate values for the newly added virtual column.
Generated at Thu Feb 08 07:31:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.