mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 20:42:30 +01:00
21809f9a45
The assertion failed in handler::ha_reset upon SELECT under READ UNCOMMITTED from table with index on virtual column. This was the debug-only failure, though the problem is mush wider: * MY_BITMAP is a structure containing my_bitmap_map, the latter is a raw bitmap. * read_set, write_set and vcol_set of TABLE are the pointers to MY_BITMAP * The rest of MY_BITMAPs are stored in TABLE and TABLE_SHARE * The pointers to the stored MY_BITMAPs, like orig_read_set etc, and sometimes all_set and tmp_set, are assigned to the pointers. * Sometimes tmp_use_all_columns is used to substitute the raw bitmap directly with all_set.bitmap * Sometimes even bitmaps are directly modified, like in TABLE::update_virtual_field(): bitmap_clear_all(&tmp_set) is called. The last three bullets in the list, when used together (which is mostly always) make the program flow cumbersome and impossible to follow, notwithstanding the errors they cause, like this MDEV-17556, where tmp_set pointer was assigned to read_set, write_set and vcol_set, then its bitmap was substituted with all_set.bitmap by dbug_tmp_use_all_columns() call, and then bitmap_clear_all(&tmp_set) was applied to all this. To untangle this knot, the rule should be applied: * Never substitute bitmaps! This patch is about this. orig_*, all_set bitmaps are never substituted already. This patch changes the following function prototypes: * tmp_use_all_columns, dbug_tmp_use_all_columns to accept MY_BITMAP** and to return MY_BITMAP * instead of my_bitmap_map* * tmp_restore_column_map, dbug_tmp_restore_column_maps to accept MY_BITMAP* instead of my_bitmap_map* These functions now will substitute read_set/write_set/vcol_set directly, and won't touch underlying bitmaps. |
||
|---|---|---|
| .. | ||
| cmake | ||
| mysql-test/oqgraph | ||
| CMakeLists.txt | ||
| graphcore-config.h | ||
| graphcore-graph.cc | ||
| graphcore-graph.h | ||
| graphcore-types.h | ||
| graphcore.cc | ||
| graphcore.h | ||
| ha_oqgraph.cc | ||
| ha_oqgraph.h | ||
| oqgraph_config.h.in | ||
| oqgraph_judy.cc | ||
| oqgraph_judy.h | ||
| oqgraph_probes.d | ||
| oqgraph_shim.cc | ||
| oqgraph_shim.h | ||
| oqgraph_thunk.cc | ||
| oqgraph_thunk.h | ||
| README | ||
OQGraph storage engine v3 Copyright (C) 2007-2014 Arjen G Lentz & Antony T Curtis for Open Query, & Andrew McDonnell The Open Query GRAPH engine (OQGRAPH) is a computation engine allowing hierarchies and more complex graph structures to be handled in a relational fashion. In a nutshell, tree structures and friend-of-a-friend style searches can now be done using standard SQL syntax, and results joined onto other tables. Based on a concept by Arjen Lentz v3 implementation by Antony Curtis, Arjen Lentz, Andrew McDonnell For more information, documentation, support, enhancement engineering, see http://openquery.com/graph or contact graph@openquery.com INSTALLATION OQGraph requires at least version 1.40.0 of the Boost Graph library. To obtain a copy of the Boost library, see http://www.boost.org/ This can be obtained in Debian Wheezy by `apt-get install libboost-graph-dev` OQGraph requires libjudy - http://judy.sourceforge.net/ This can be obtained in Debian Wheezy by `apt-get install libjudy-dev` BUILD (example) cd path/to/maria/source mkdir build # use symlink to scratch cd build CONFIGURE="-DWITH_EXTRA_CHARSETS=complex -DWITH_PLUGIN_ARIA=1 -DWITH_READLINE=1 -DWITH_SSL=bundled -DWITH_MAX=1 -DWITH_EMBEDDED_SERVER=1" cmake .. $CONFIGURE make -j5 mysql-test-run --suite oqgraph