An error occurred fetching the project authors.
- 14 Mar, 2008 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
When there are no underlying tables specified for a merge table, SHOW CREATE TABLE outputs a statement that cannot be executed. The same is true for mysqldump (it generates dumps that cannot be executed). This happens because SQL parser does not accept empty UNION() clause. This patch changes the following: - it is now possible to execute CREATE/ALTER statement with empty UNION() clause. - the same as above, but still worth noting: it is now possible to remove underlying tables mapping using ALTER TABLE ... UNION=(). - SHOW CREATE TABLE does not output UNION() clause if there are no underlying tables specified for a merge table. This makes mysqldump slightly smaller.
-
- 12 Dec, 2007 1 commit
-
-
istruewing@stella.local authored
Fixed case of comment.
-
- 26 Nov, 2007 1 commit
-
-
kaa@polly.(none) authored
self-join When doing DELETE with self-join on a MyISAM or MERGE table, it could happen that a record being retrieved in join_read_next_same() has already been deleted by previous iterations. That caused the engine's index_next_same() method to fail with HA_ERR_RECORD_DELETED error and the whole DELETE query to be aborted with an error. Fixed by suppressing the HA_ERR_RECORD_DELETED error in hy_myisam::index_next_same() and ha_myisammrg::index_next_same(). Since HA_ERR_RECORD_DELETED can only be returned by MyISAM, there is no point in filtering this error in the SQL layer.
-
- 09 Oct, 2007 1 commit
-
-
istruewing@stella.local authored
Added test case. The fix for Bug#20662 does also fix this one.
-
- 05 Jun, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
SHOW CREATE TABLE fails Underlying table names, that merge engine fails to open were not reported. With this fix CHECK TABLE issued against merge table reports all underlying table names that it fails to open. Other statements are unaffected, that is underlying table names are not included into error message. This fix doesn't solve SHOW CREATE TABLE issue.
-
- 10 Apr, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
MERGE engine may return incorrect values when several representations of equal keys are present in the index. For example "groß" and "gross" or "gross" and "gross " (trailing space), which are considered equal, but have different lengths. The problem was that key length was not recalculated after key lookup. Only MERGE engine is affected.
-
- 20 Mar, 2007 1 commit
-
-
holyfoot/hf@mysql.com/hfmain.(none) authored
-
- 13 Mar, 2007 1 commit
-
-
svoj@mysql.com/april.(none) authored
differences in tables Certain merge tables were wrongly reported as having incorrect definition: - Some fields that are 1 byte long (e.g. TINYINT, CHAR(1)), might be internally casted (in certain cases) to a different type on a storage engine layer. (affects 4.1 and up) - If tables in a merge (and a MERGE table itself) had short VARCHAR column (less than 4 bytes) and at least one (but not all) tables were ALTER'ed (even to an identical table: ALTER TABLE xxx ENGINE=yyy), table definitions went ouf of sync. (affects 4.1 only) This is fixed by relaxing a check for underlying conformance and setting field type to FIELD_TYPE_STRING in case varchar is shorter than 4 when a table is created.
-
- 05 Mar, 2007 1 commit
-
-
istruewing@chilla.local authored
Using INSERT DELAYED on MERGE tables could lead to table corruptions. The manual lists a couple of storage engines, which can be used with INSERT DELAYED. MERGE is not in this list. The attempt to try it anyway has not been rejected yet. This bug was not detected earlier as it can work under special circumstances. Most notable is low concurrency. To be safe, this patch rejects any attempt to use INSERT DELAYED on MERGE tables.
-
- 31 Jan, 2007 1 commit
-
-
svoj@mysql.com/june.mysql.com authored
When a merge table is opened compare column and key definition of underlying tables against column and key definition of merge table. If any of underlying tables have different column/key definition refuse to open merge table.
-
- 28 Sep, 2006 1 commit
-
-
svoj@mysql.com/april.(none) authored
Crash may happen when selecting from a merge table that has underlying tables with less indexes than in a merge table itself. If number of keys in merge table is not bigger than requested key number, return error.
-
- 19 Sep, 2006 1 commit
-
-
svoj@mysql.com/april.(none) authored
Fixed confusing error message from the storage engine when it fails to open underlying table. The error message is issued when a table is _opened_ (not when it is created).
-
- 12 Jul, 2006 1 commit
-
-
jimw@rama.(none) authored
Changed the error reporting (and a crash) when inserting data into a MERGE table that has no underlying tables or no INSERT_METHOD specified by reporting that it is read-only.
-
- 10 Jul, 2006 1 commit
-
-
ingo/mydev@chilla.local authored
-
- 31 May, 2006 1 commit
-
-
acurtis@xiphis.org authored
"Merge table does not work with bit types" MERGE should have HA_CAN_BIT_FIELD feature bit set or else table row is formatted incorrectly.
-
- 09 May, 2006 1 commit
-
-
acurtis@xiphis.org authored
"alter table from MyISAM to MERGE lost data without errors and warnings" Add new handlerton flag which prevent user from altering table storage engine to storage engines which would lose data. Both 'blackhole' and 'merge' are marked with the new flag. Tests included.
-
- 20 Dec, 2005 1 commit
-
-
ingo@mysql.com authored
Problem #1: INSERT...SELECT, Version for 5.0. Extended the unique table check by a check of lock data. Merge sub-tables cannot be detected by doing name checks only.
-
- 07 Dec, 2005 1 commit
-
-
ingo@mysql.com authored
Problem #1: INSERT...SELECT, Version for 4.1. INSERT ... SELECT with the same table on both sides (hidden below a MERGE table) does now work by buffering the select result. The duplicate detection works now after open_and_lock_tables() on the locks. I did not find a test case that failed without the change in sql_update.cc. I made the change anyway as it should in theory fix a possible MERGE table problem with multi-table update.
-
- 29 Nov, 2005 1 commit
-
-
ingo@mysql.com authored
Problem #1: INSERT...SELECT INSERT ... SELECT with the same table on both sides (hidden below a MERGE table) does now work by buffering the select result. The duplicate detection works now after open_and_lock_tables() on the locks. I did not find a test case that failed without the change in sql_update.cc. I made the change anyway as it should in theory fix a possible MERGE table problem with multi-table update.
-
- 29 Sep, 2005 1 commit
-
-
ingo@mysql.com authored
Second platform fix for floating point rounding.
-
- 27 Sep, 2005 1 commit
-
-
ingo@mysql.com authored
Reduced the precision of the test numbers. Not all platforms could reproduce the exact numbers.
-
- 23 Sep, 2005 2 commits
-
-
ingo@mysql.com authored
After merge fix
-
ingo@mysql.com authored
The problem was an ab-use of last_rkey_length. Formerly we saved the packed key length (of the search key) in this element. But in certain cases it got replaced by the (packed) result key length. Now we use a new element of MI_INFO to save the packed key length of the search key.
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 18 May, 2005 1 commit
-
-
ingo@mysql.com authored
After review version. Added a condition for MERGE tables. These do not have unique indexes. But every key could be a unique key on the underlying MyISAM table. So get the maximum key length for MERGE tables instead of the maximum unique key length. This is used for buffer allocation in write_record().
-
- 27 Dec, 2004 1 commit
-
-
timour@mysql.com authored
Fix for BUG#7377. This fix adds the same implementation for ha_myisammgr::index_type as in version 5.0.
-
- 23 Dec, 2004 1 commit
-
-
ingo@mysql.com authored
Changed my_error() to print error messages, which come from arbitrary registered ranges of error messages. Messages can be unregistered (and should be at end of the program). Added registration of handler error messages. Added a new mi_print_error() macro and a new mi_report_error() function, which supply error messages with a table name. Added calls to mi_print_error() or mi_report_error() at all places in MyISAM, where table corruption is detected.
-
- 29 Nov, 2004 1 commit
-
-
sergefp@mysql.com authored
-
- 09 Sep, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 27 Aug, 2004 1 commit
-
-
ram@gw.mysql.r18.ru authored
-
- 25 Jun, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 04 Mar, 2004 1 commit
-
-
serg@serg.mylan authored
-
- 10 Dec, 2003 1 commit
-
-
Deprecate the use of TYPE=... Preferred syntax is ENGINE=
-
- 03 Jul, 2003 1 commit
-
-
monty@narttu.mysql.fi authored
Tests cleanup (put drop database first in tests)
-
- 01 Jul, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
-
- 27 Jun, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Added command 'replace_column' to mysqltest
-
- 16 Jan, 2003 1 commit
-
-
serg@serg.mysql.com authored
-
- 05 Jan, 2003 1 commit
-
-
monty@mashka.mysql.fi authored
Cleaned up test; Removed wrong DROP TABLE commands and use standard table and database names. changed store_warning() -> push_warning_print()
-
- 14 Dec, 2002 1 commit
-
-
monty@mashka.mysql.fi authored
Changed timestamp to return string in YYYY-MM-DD HH:MM:SS format. DATE_ADD() and related functions now returns correct DATE/DATETIME type depending on argument types. Now all tests passes, still some work left to remove warnings in log files from mysql-test-run
-
- 17 Nov, 2002 1 commit
-
-
serg@serg.mysql.com authored
-