Comments - ERROR 1932 on a table with recently added VIRTUAL column

8 years, 9 months ago Jan Steinman

Okay, a second table with a recently added VIRTUAL column is now doing the same thing.

I'm about to back out MariaDB and return to MySQL. Any ideas about what's going on here? Are VIRTUAL columns unstable?

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.