Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SQL export includes values for virtual fields #5
Exporting SQL to other database without error when table contains virtual column.
MySQL SQL Error (3105) error thrown during SQL export to other database when table contains virtual column.
Failure information (for bugs)
Error message: "SQL Error (3105): The value specified for generated column 'computed_column_name' in table 'table_name' is not allowed."
Snippet for column:
Steps to reproduce
Please provide detailed steps for reproducing the issue.
The table in question has a column with a simple formula: "AS (columnA + columnB * + columnC)"
The problem that HeidiSQL generates the following command during the Export process that contains the virtual column and values as well:
According to Roy Lyseng the insert command should look like this (without the virtual column):
Roy wrote that this is not a MySQL bug so it must be handled on the client (HeidiSQL) side.
Use triggers instead of virtual columns.
MySQL exception thrown.