An error occurred fetching the project authors.
- 29 Dec, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 10 Dec, 2004 4 commits
-
-
heikki@hundin.mysql.fi authored
Remove accidentally merged 4.0 changes dict0dict.c: Remove the 4.0 fix accidentally auto-merged to 4.1 row0mysql.h, dict0dict.h: Remove a change auto-merged from 4.0
-
heikki@hundin.mysql.fi authored
Fix for the 0xA0 character problem in the InnoDB FOREIGN KEY parser: if my_isspace() treats 0xA0 as space, then let InnoDB do the same; this might break some multi-byte charset id's, though for big5, ujis, sjis this seems not to change the current behavior (I checked the tables in /share/charsets); this fix must NOT be merged to 4.1 because in 4.1 everything is in UTF-8
-
heikki@hundin.mysql.fi authored
In the FOREIGN KEY parser, do not cut 0xC2A0 from the end of an identifier if it was quoted
-
heikki@hundin.mysql.fi authored
Fix the bug that the character 0xA0 that EMS MySQL Manager in ALTER TABLE adds after a table name confuses the InnoDB FOREIGN KEY parser, causing an error 121 when we try to add a new constraint; a full fix would require the lexer to be aware of thd->charset_info() and UTF-8
-
- 02 Dec, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
Implement more compact InnoDB record format. Old format is available as CREATE TABLE ... ROW_FORMAT=DYNAMIC.
-
- 03 Nov, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 31 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it dict0dict.c: Fix bug #3478: InnoDB's FOREIGN KEY tables treated table and database names as case-insensitive; RENAME TABLE t to T would hang in an endless loop if t had a foreign key constraint defined on it; fix also a hang that would occur if one tried in ALTER TABLE or RENAME TABLE to create a foreign key constraint name that collided with another existing name
-
- 18 Oct, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 14 Oct, 2004 1 commit
-
-
jan@hundin.mysql.fi authored
X-locks on duplicates also on LOAD DATA...REPLACE clause and fixes a bug #6086 adding --disable_warnings and --enable_warnings around the create table clauses in ctype_utf8 tests for InnoDB.
-
- 07 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #5137: if innodb_file_per_table was specified, CREATE TEMPORARY TABLE ... TYPE=InnoDB said that cannot find path specified, and made mysqld to exit(1)
-
- 04 Oct, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 01 Oct, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 16 Sep, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #5180: having a column prefix index in the primary key, and the same column fully in a secondary key could cause an assertion failure in row_build_row_ref()
-
- 10 Sep, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
Fixed typo
-
- 08 Sep, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 06 Aug, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
InnoDB: Implement tmpfile() differently on Windows (Bug #3998)
-
- 17 Jun, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
-
- 16 Jun, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
be needed when testing production releases
-
- 28 May, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 27 May, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
Disable log archiving code unless #ifdef UNIV_LOG_ARCHIVE Remove (char*) casts of string constants; add const qualifiers Remove some Hot Backup code unless #ifdef UNIV_HOTBACKUP
-
- 17 May, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
Allocate the table name buffer from the mem heap of a foreign key object rather than pointing to the name buffer in the table object; even though this apparently caused no bugs in RENAME, DROP, ALTER TABLE, or elsewhere, this convention was very prone to memory allocation bugs
-
marko@hundin.mysql.fi authored
-
- 13 May, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 07 Apr, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 06 Apr, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
instead of stdout or fixed-size memory buffers
-
- 02 Apr, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
when dropping database (Bug #3058)
-
- 01 Apr, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 31 Mar, 2004 2 commits
-
-
marko@hundin.mysql.fi authored
-
marko@hundin.mysql.fi authored
-
- 30 Mar, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 17 Mar, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
Fix Bug #1942: do not retrieve all columns in a table if we only need the 'ref' of the row (usually, the PRIMARY KEY) to calculate an ORDER BY
-
monty@mysql.com authored
-
- 13 Mar, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 12 Mar, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 11 Mar, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 09 Feb, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Allow always DROPping of a table which is only referenced by FOREIGN KEY constraints from the same table Many files: Do not let REPLACE to perform internally an UPDATE if the table is referenced by a FOREIGN KEY: the manual says that REPLACE must resolve a duplicate key error semantically with DELETE(s) + INSERT, and not by an UPDATE; the internal update caused foreign key checks and cascaded operations to behave in a semantically wrong way
-
- 08 Feb, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication sync0sync.c: UNIV_SYNC_DEBUG caused assertion in the creation of the doublewrite buffer, if we do not allow thousands of latches per thread
-
- 01 Feb, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
Change print format of FOREIGN KEY constraints spanning multiple databases to <backquote>databasename<backquote>.<backquote>tablename<backquote>; but when parsing them we must also accept <backquote>databasename.tablename<backquote>, because that was the output format in < 4.0.18
-
heikki@hundin.mysql.fi authored
Change print format of FOREIGN KEY constraints spanning multiple databases to: .; but we when parsing them we must also accept , because that was the output format in < 4.0.18
-