An error occurred fetching the project authors.
- 08 Nov, 2004 1 commit
-
-
jan@hundin.mysql.fi authored
locks all rows (BUG #3300). When using innobase_locks_unsafe_for_binlog option InnoDB does not take locks for those rows which do not belong to the result set or werent changed by the query. This fix removes unnecessary locks also from SELECT and DELETE queries.
-
- 27 Oct, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 26 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Print more warnings to the .err log if ALTER TABLE ... IMPORT TABLESPACE fails for some reason os0file.c: Do not call exit(1) if os_file_delete() fails; remove unused parameter from handle_error_no_exit() fil0fil.c: Allow DROP TABLE even if the .ibd file for the table does not exist
-
- 21 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #5961: release the dictionary latch during a long cascaded FOREIGN KEY operation, so that we do not starve other users
-
- 08 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
If one tries to drop an InnoDB table without an .ibd file, print to .err log that we DID remove the table from the internal data dictionary of InnoDB, and return DB_SUCCESS so that MySQL will delete the .frm file; the drawback in this is that then DROP TABLE returns success, and the user is not alerted; maybe it could return a warning
-
- 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)
-
- 05 Oct, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Raise maximum column prefix len to 767 bytes, so that MySQL can create a column prefix index of 255 UTF-8 characters (each takes 3 bytes at the maximum); add comments about why innobase_get_at_most_n_mbchars() works ok dict0mem.h: Raise maximum column prefix len to 767 bytes, so that MySQL can create a column prefix index of 255 UTF-8 characters (each takes 3 bytes at the maximum) row0mysql.c: If MySQL tries to create a column prefix index longer that 255 UTF-8 characters, give an error, and drop the table from the InnoDB internal data dictionary. MySQL did not drop the table there in its own error handling.
-
- 04 Oct, 2004 2 commits
-
-
marko@hundin.mysql.fi authored
-
marko@hundin.mysql.fi authored
-
- 01 Oct, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 30 Sep, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 08 Sep, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 01 Sep, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
row_drop_table_for_mysql(): Removed duplicated block of code.
-
- 13 Aug, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug: if we RENAME a table, InnoDB forgot to load the foreign key constraints that reference the new table name, and forgot to check that they are compatible with the table
-
- 09 Aug, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
row_drop_table_for_mysql(): Removed a ut_ad() assertion that failed when a DROP TABLE is executed in the background.
-
- 12 Jul, 2004 2 commits
-
-
marko@hundin.mysql.fi authored
-
marko@hundin.mysql.fi authored
(Bug #2694)
-
- 15 Jun, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 01 Jun, 2004 2 commits
-
-
heikki@hundin.mysql.fi authored
Inside LOCK TABLES, use either LOCK_S or LOCK_X in locking reads; an improvent over the previous patch
-
marko@hundin.mysql.fi authored
allow deletion of tablespaces whose names contain "'"
-
- 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 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 10 May, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 07 May, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 29 Apr, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 27 Apr, 2004 1 commit
-
-
monty@mishka.local authored
Changed 'SHOW FIELD STATUS' to use 'Engine' instead of 'Type'
-
- 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 1 commit
-
-
marko@hundin.mysql.fi authored
-
- 17 Mar, 2004 1 commit
-
-
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
-
- 20 Feb, 2004 1 commit
-
-
marko@hundin.mysql.fi authored
Removed unused code .del-os0trash.c~8cae5c1695501117: Delete: innobase/os/os0trash.c dict0crea.c: Protect all sprintf(%s) with assertions
-
- 09 Feb, 2004 2 commits
-
-
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
-
heikki@hundin.mysql.fi authored
Fix crash in InnoDB RENAME TABLE if 'databasename/tablename' is shorter than 5 characters (Bug #2689); reported by Sergey Petrunia
-
- 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 1 commit
-
-
heikki@hundin.mysql.fi authored
Remove redundant code; parse both the database name and the table name in a FOREIGN KEY constraint with quotes in mind row0mysql.c, ha_innodb.cc, sql_table.cc: Return error message Cannot delete or update a parent row... if we try to drop a table which is referenced by a FOREIGN KEY constraint, and the user has not set foreign_key_checks=0
-
- 08 Jan, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix typo
-