mirror of
https://github.com/MariaDB/server.git
synced 2025-01-29 18:20:07 +01:00
4090100743
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(). |
||
|---|---|---|
| .. | ||
| rpl_vcol.result | ||
| vcol_archive.result | ||
| vcol_blackhole.result | ||
| vcol_blocked_sql_funcs_innodb.result | ||
| vcol_blocked_sql_funcs_myisam.result | ||
| vcol_column_def_options_innodb.result | ||
| vcol_column_def_options_myisam.result | ||
| vcol_csv.result | ||
| vcol_handler_innodb.result | ||
| vcol_handler_myisam.result | ||
| vcol_ins_upd_innodb.result | ||
| vcol_ins_upd_myisam.result | ||
| vcol_keys_innodb.result | ||
| vcol_keys_myisam.result | ||
| vcol_memory.result | ||
| vcol_merge.result | ||
| vcol_misc.result | ||
| vcol_non_stored_columns_innodb.result | ||
| vcol_non_stored_columns_myisam.result | ||
| vcol_partition_innodb.result | ||
| vcol_partition_myisam.result | ||
| vcol_select_innodb.result | ||
| vcol_select_myisam.result | ||
| vcol_supported_sql_funcs_innodb.result | ||
| vcol_supported_sql_funcs_myisam.result | ||
| vcol_syntax.result | ||
| vcol_trigger_sp_innodb.result | ||
| vcol_trigger_sp_myisam.result | ||
| vcol_view_innodb.result | ||
| vcol_view_myisam.result | ||