An error occurred fetching the project authors.
- 08 Mar, 2007 1 commit
-
-
istruewing@chilla.local authored
incorrect key file for table In certain cases it could happen that deleting a row could corrupt an RTREE index. According to Guttman's algorithm, page underflow is handled by storing the page in a list for later re-insertion. The keys from the stored pages have to be inserted into the remaining pages of the same level of the tree. Hence the level number is stored in the re-insertion list together with the page. In the MySQL RTree implementation the level counts from zero at the root page, increasing numbers for levels down the tree. If during re-insertion of the keys the tree height grows, all level numbers become invalid. The remaining keys will be inserted at the wrong level. The fix is to increment the level numbers stored in the reinsert list after a split of the root block during reinsertion.
-
- 19 Dec, 2006 1 commit
-
-
gkodinov/kgeorge@macbook.gmz authored
spatial index While executing OPTIMIZE TABLE on MyISAM tables the server re-creates the index file(s) in order to sort them physically by the key. This cannot be done for R-tree indexes as it makes no sense. The server was not checking the type of the index and was accessing an R-tree index as if it was a B-tree. Fixed by preventing sorting the index file if it contains an R-tree index.
-
- 01 Oct, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
We issued UNKNOWN ERROR initially in this place and forgot to fix it when we implemented informative error message for this
-
- 29 Sep, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
RTree keys are really different from BTree and need specific paramters to be set by optimizer to work. Sometimes optimizer doesn't set those properly. Here we decided just to add code to check that the parameters are correct. Hope to fix optimizer sometimes.
-
- 28 Jun, 2006 1 commit
-
-
ingo@mysql.com authored
CHECK TABLE could complain about a fully intact spatial index. A wrong comparison operator was used for table checking. The result was that it checked for non-matching spatial keys. This succeeded if at least two different keys were present, but failed if only the matching key was present. I fixed the key comparison.
-
- 09 Aug, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 29 Apr, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 15 Jan, 2005 1 commit
-
-
jimw@mysql.com authored
are not specified in an insert. Most of these changes are actually to clean up the test suite to either specify defaults to avoid warnings, or add the warnings to the results. Related to bug #5986.
-
- 10 Dec, 2004 1 commit
-
-
hf@deer.(none) authored
(after discussion with SerG)
-
- 06 Dec, 2004 1 commit
-
-
hf@deer.(none) authored
-
- 27 May, 2004 1 commit
-
-
hf@deer.(none) authored
--with-geometry and --with-embedded-privilege-control configure switches added
-
- 08 Apr, 2004 1 commit
-
-
monty@mysql.com authored
This gives the handler more optimization possiblities and is needed for NDB cluster Fixed not-initialized memory error detected by valgrind
-
- 19 Feb, 2004 1 commit
-
-
hf@deer.(none) authored
Now checking of the RTree keys works without errors. Worklog entry about appropriate checkup's routine for the RTree added
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 18 Mar, 2003 1 commit
-
-
ram@mysql.r18.ru authored
-
- 12 Mar, 2003 1 commit
-
-
ram@mysql.r18.ru authored
-