An error occurred fetching the project authors.
- 19 Nov, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
SPATIAL key is fine actually, but the chk_key() function mistakenly returns error. It tries to compare checksums of btree and SPATIAL keys while the checksum for the SPATIAL isn't calculated (always 0). Same thing with FULLTEXT keys is handled using full_text_keys counter, so fixed by counting both SPATIAL and FULLTEXT keys in that counter.
-
- 06 Nov, 2007 1 commit
-
-
istruewing@stella.local authored
Disabling and enabling indexes on a non-empty table grows the index file. Disabling indexes just sets a flag per non-unique index and does not free the index blocks of the affected indexes. Re-enabling indexes creates new indexes with new blocks. The old blocks remain unused in the index file. Fixed by dropping and re-creating all indexes if non-empty disabled indexes exist when enabling indexes. Dropping all indexes resets the internal end-of-file marker to the end of the index file header. It also clears the root block pointers of every index and clears the deleted blocks chains. This way all blocks are declared as free.
-
- 16 May, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
tables In case system doesn't have native pread/pwrite calls (e.g. Windows) and there is CHECK TABLE runs concurrently with another statement that reads from a table, the table may be reported as crashed. This is fixed by locking file descriptor when my_seek is executed on MyISAM index file and emulated pread/pwrite may be executed concurrently. Affects MyISAM tables on platforms that do not have native pread/pwrite calls (e.g. Windows). No deterministic test case for this bug.
-
- 31 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Corrected spelling in copyright text Makefile.am: Don't update the files from BitKeeper Many files: Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header Adjusted year(s) in copyright header Many files: Added GPL copyright text Removed files: Docs/Support/colspec-fix.pl Docs/Support/docbook-fixup.pl Docs/Support/docbook-prefix.pl Docs/Support/docbook-split Docs/Support/make-docbook Docs/Support/make-makefile Docs/Support/test-make-manual Docs/Support/test-make-manual-de Docs/Support/xwf
-
- 23 Dec, 2006 1 commit
-
-
kent@mysql.com/kent-amd64.(none) authored
Changed header to GPL version 2 only
-
- 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.
-
- 25 Oct, 2006 1 commit
-
-
istruewing@chilla.local authored
When compiling with a default key block size greater than the smallest key block size used in a table, checking that table failed with bogus errors. The table was marked corrupt. This affected myisamchk and the server. The problem was that the default key block size was used at some places where sizes less or equal to the block size of the index in check was required. We do now use the key block size of the particular index when checking. A test case is available for later versions only.
-
- 09 Oct, 2006 1 commit
-
-
istruewing@chilla.local authored
OPTIMIZE TABLE with myisam_repair_threads > 1 performs a non-quick parallel repair. This means that it does not only rebuild all indexes, but also the data file. Non-quick parallel repair works so that there is one thread per index. The first of the threads rebuilds also the new data file. The problem was that all threads shared the read io cache on the old data file. If there were holes (deleted records) in the table, the first thread skipped them, writing only contiguous, non-deleted records to the new data file. Then it built the new index so that its entries pointed to the correct record positions. But the other threads didn't know the new record positions, but put the positions from the old data file into the index. The new design is so that there is a shared io cache which is filled by the first thread (the data file writer) with the new contiguous records and read by the other threads. Now they know the new record positions. Another problem was that for the parallel repair of compressed tables a common bit_buff and rec_buff was used. I changed it so that thread specific buffers are used for parallel repair. A similar problem existed for checksum calculation. I made this multi-thread safe too.
-
- 06 Sep, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
-
- 04 Sep, 2006 1 commit
-
-
holyfoot/hf@mysql.com/deer.(none) authored
The problem is that on some Mac OS X-es the file writing/reading call with zero bytes to read/write returns error. So here i try to eliminate that kinds of calls.
-
- 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.
-
- 31 May, 2006 1 commit
-
-
ingo@mysql.com authored
CHECK TABLE did temporarily clear the auto_increment value. It runs with a read lock, allowing other readers and conurrent INSERTs. The latter could grab the wrong value in this moment. CHECK TABLE does no longer modify the auto_increment value. Not even for a short moment.
-
- 10 Apr, 2006 1 commit
-
-
ingo@mysql.com authored
Whenever 'myisamchk' needed to recreate a table, the auto increment information was lost. Now the forgotten element of the table creation information is set correctly.
-
- 23 Nov, 2005 1 commit
-
-
SergeyV@selena. authored
table statistics is not updated, so the next execution of analyze table will try to update statistics again.
-
- 01 Nov, 2005 1 commit
-
-
monty@mysql.com authored
Removed wrong fix for bug #14009 (use of abs() on null value causes problems with filesort) Mark that add_time(), time_diff() and str_to_date() can return null values
-
- 26 Oct, 2005 1 commit
-
-
ingo@mysql.com authored
Bug#12166 - Unable to index very large tables Moved clearing of errors behind the second repair attempt, but will clear only if no error happened. No test case. The error can be repeated with little free space on tmpdir only. I do not know of a way to create this in a portable way with our test suite. I did however attach a shell script to the bug report which can easily be adapted to the situation on the test machine.
-
- 25 Oct, 2005 1 commit
-
-
jani@ua141d10.elisa.omakaista.fi authored
-
- 24 Oct, 2005 1 commit
-
-
monty@mysql.com authored
-
- 22 Oct, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 21 Oct, 2005 1 commit
-
-
sergefp@mysql.com authored
added "nulls_ignored" index statistics collection method for MyISAM tables. (notification trigger: this is about BUG#9622).
-
- 27 Sep, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 23 Sep, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 20 Sep, 2005 1 commit
-
-
sergefp@mysql.com authored
statistics (like 4.0 did) (patch #3, with review #1 & #2 feedback addressed)
-
- 09 Sep, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 05 Sep, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 09 Aug, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 19 Jul, 2005 1 commit
-
-
ingo@mysql.com authored
This patch allows to configure MyISAM for 128 indexes per table. The main problem is the key_map, wich is implemented as an ulonglong. To get rid of the limit and keep the efficient and flexible implementation, the highest bit is now used for all upper keys. This means that the lower keys can be disabled and enabled individually as usual and the high keys can only be disabled and enabled as a block. That way the existing test suite is still applicable, while more keys work, though slightly less efficient. To really get more than 64 keys, some defines need to be changed. Another patch will address this.
-
- 03 Jun, 2005 2 commits
-
-
mronstrom@mysql.com authored
After review fix Copy from internal state to share state only when in lock write mode (happens only when lock table x write has been performed since update_state_info is only called when holding a TL_READ_NO_INSERT lock normally. Previous patch would have failed in combination with delayed writes.
-
mronstrom@mysql.com authored
Analyze table corrupts the state on data_file_length, records, index_file_length... by writing the shared state when there is an updated internal state due to inserts or deletes Fixed by synching the shared state with the internal state before writing it to disk Added test cases of 2 error cases and a normal case in new analyze test case
-
- 13 May, 2005 1 commit
-
-
sergefp@mysql.com authored
way in ALTER TABLE ... ENABLE KEYS, ANALYZE TABLE and after bulk insert: now statistics collection always assumes NULLs are inequal.
-
- 11 Apr, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 03 Jan, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 18 Dec, 2004 1 commit
-
-
monty@mysql.com authored
Add support for VARCHAR with 1 or 2 length bytes Enable VARCHAR packing in MyISAM files (previous patch didn't pack data properly) Give error if we got problems in temporary tables during a SELECT Don't use new table generated by ALTER TABLE if index generation fails Fixed wrong call by range_end() (Could cause an ASSERT in debug mode)
-
- 06 Dec, 2004 2 commits
-
-
hf@deer.(none) authored
-
monty@mysql.com authored
Renamed HA_VAR_LENGTH to HA_VAR_LENGTH_PART Renamed in all files FIELD_TYPE_STRING and FIELD_TYPE_VAR_STRING to MYSQL_TYPE_STRING and MYSQL_TYPE_VAR_STRING to make it easy to catch all possible errors Added support for VARCHAR KEYS to heap Removed support for ISAM Now only long VARCHAR columns are changed to TEXT on demand (not CHAR) Internal temporary files can now use fixed length tables if the used VARCHAR columns are short
-
- 12 Nov, 2004 1 commit
-
-
monty@mysql.com authored
-
- 11 Nov, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 29 Oct, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 22 Sep, 2004 1 commit
-
-
sergefp@mysql.com authored
* myisampack leaves key_file_length value from original table * myisamchk uses this value when calculating key file pointer length
-
- 03 Sep, 2004 1 commit
-
-
serg@serg.mylan authored
-