1
0
mirror of https://github.com/MariaDB/server.git synced 2025-07-30 16:24:05 +03:00
There were two problems that caused wrong results reported with this bug.
1. In some cases stored(persistent) virtual columns were not marked
in the write_set and in the vcol_set bitmaps.
2. If the list of fields in an insert command was empty then the values of
the stored virtual columns were set to default.

To fix the first problem the function st_table::mark_virtual_columns_for_write
was modified. Now the function has a parameter that says whether the virtual 
columns are to be marked for insert or for update.  
To fix the second problem a special handling of empty insert lists is
added in the function fill_record().
This commit is contained in:
Igor Babaev
2010-07-15 16:51:05 -07:00
parent 683154d1fa
commit 4090100743
9 changed files with 81 additions and 17 deletions

View File

@ -532,6 +532,13 @@ public:
bool describe; /* union exec() called for EXPLAIN */
Procedure *last_procedure; /* Pointer to procedure, if such exists */
/*
Insert table with stored virtual columns.
This is used only in those rare cases
when the list of inserted values is empty.
*/
TABLE *insert_table_with_stored_vcol;
void init_query();
st_select_lex_unit* master_unit();
st_select_lex* outer_select();