| Bug #80299 | DEFAULT is not deterministic and should not be allowed in generated columns | ||
|---|---|---|---|
| Submitted: | 8 Feb 2016 9:04 | Modified: | 25 Mar 2016 14:02 | 
| Reporter: | Roy Lyseng | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) | 
| Version: | 5.7.11 | OS: | Any | 
| Assigned to: | CPU Architecture: | Any | |
   [8 Feb 2016 9:04]
   Roy Lyseng        
  
 
   [8 Feb 2016 9:38]
   MySQL Verification Team        
  Hello Roy, Thank you for the report. Thanks, Umesh
   [25 Mar 2016 14:02]
   Paul DuBois        
  Posted by developer: Noted in 5.7.13, 5.8.0 changelogs. It is possible to use ALTER TABLE to change the default value of a column col_name, which may change the value of a generated column expression that refers to the column using DEFAULT(col_name). For this reason, ALTER TABLE operations that change the default value of col_name now cause a table rebuild if any generated column expression uses DEFAULT(col_name).
   [29 Mar 2016 14:33]
   Paul DuBois        
  Revised changelog entry: It is possible to use ALTER TABLE to change the default value of a column col_name, which may change the value of a generated column expression that refers to the column using DEFAULT(col_name). For this reason, ALTER TABLE operations that change the definition of a column now cause a table rebuild if any generated column expression uses DEFAULT().
