diff options
| author | unknown <istruewing@chilla.local> | 2007-03-19 15:56:53 +0100 |
|---|---|---|
| committer | unknown <istruewing@chilla.local> | 2007-03-19 15:56:53 +0100 |
| commit | db573e637c2ba66f214f7e1e2172ce9efeca0db0 (patch) | |
| tree | 5c48ed97050e9f6a5b2a0da2a264d7d9d3b1084e /heap | |
| parent | da9c659c8196d1da63330fc7b1b6710217801a6f (diff) | |
| download | mariadb-git-db573e637c2ba66f214f7e1e2172ce9efeca0db0.tar.gz | |
Bug#26996 - Update of a Field in a Memory Table ends with wrong result
Using a MEMORY table BTREE index for scanning for updatable rows
could lead to an infinite loop.
Everytime a key was inserted into a btree index, the position
in the index scan was cleared. The search started from the
beginning and found the same key again.
Now we do not clear the position on key insert an more.
heap/hp_write.c:
Bug#26996 - Update of a Field in a Memory Table ends with wrong result
Removed the index-scan-breaking nulling of last_pos.
The comment behind this line ("For heap_rnext/heap_rprev")
was misleading. It should have been "Breaks heap_rnext/heap_rprev".
mysql-test/r/heap_btree.result:
Bug#26996 - Update of a Field in a Memory Table ends with wrong result
Added test result.
mysql-test/t/heap_btree.test:
Bug#26996 - Update of a Field in a Memory Table ends with wrong result
Added test.
Diffstat (limited to 'heap')
| -rw-r--r-- | heap/hp_write.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/heap/hp_write.c b/heap/hp_write.c index 841dda6264e..59dfca31fd9 100644 --- a/heap/hp_write.c +++ b/heap/hp_write.c @@ -106,7 +106,6 @@ int hp_rb_write_key(HP_INFO *info, HP_KEYDEF *keyinfo, const byte *record, heap_rb_param custom_arg; uint old_allocated; - info->last_pos= NULL; /* For heap_rnext/heap_rprev */ custom_arg.keyseg= keyinfo->seg; custom_arg.key_length= hp_rb_make_key(keyinfo, info->recbuf, record, recpos); if (keyinfo->flag & HA_NOSAME) |