- 16 Feb, 2004 4 commits
-
-
monty@mysql.com authored
-
monty@mysql.com authored
Added more DBUG statements Ensure that we are comparing end space with BINARY strings Use 'any_db' instead of '' to mean any database. (For HANDLER command) Only strip ' ' when comparing CHAR, not other space-like characters (like \t)
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
- 14 Feb, 2004 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
- 13 Feb, 2004 1 commit
-
-
monty@mysql.com authored
Always use all LOAD DATA options in replication. Fixed problem in mysqlbinlog where LOAD DATA options could be overwritten.
-
- 12 Feb, 2004 8 commits
-
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2898/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2898/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
-
lenz@mysql.com authored
- Tagged ChangeSet@1.1733 as mysql-4.0.18
-
lenz@mysql.com authored
-
lenz@mysql.com authored
-
lenz@mysql.com authored
on libstdc++ and exceptions
-
- 11 Feb, 2004 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.0
-
- 10 Feb, 2004 9 commits
-
-
monty@mysql.com authored
-
jani@ua141d10.elisa.omakaista.fi authored
caused UDF functions to segmenation fault when they tried to print an error during wrong usage.
-
jani@ua141d10.elisa.omakaista.fi authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
-
konstantin@mysql.com authored
-
monty@mysql.com authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
-
bell@sanja.is.com.ua authored
-
- 09 Feb, 2004 12 commits
-
-
guilhem@gbichot2.local authored
Don't use --command in tests; use command.
-
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
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.1-root
-
konstantin@oak.local authored
don't set other flags: it breaks future extensions
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
-
monty@mysql.com authored
Removed warnings from test suite
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
-
monty@mysql.com authored
Fixed output from mysqlbinlog when using --skip-comments Fixed warnings from valgrind Fixed ref_length when used with HEAP tables More efficent need_conversion() Fixed error handling in UPDATE with not updateable tables Fixed bug in null handling in CAST to signed/unsigned
-
konstantin@mysql.com authored
alter table rename a bit more efficient in case of lower_case_table_names.
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-derived2-4.1
-
- 08 Feb, 2004 2 commits
-
-
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
-
heikki@hundin.mysql.fi authored
If AUTOCOMMIT=1, then we do not need to make a plain SELECT set shared locks even on the SERIALIZABLE isolation level, because we know the transaction is read-only: a read-only transaction can always be performed on the REPEATABLE READ level, and that does not endanger the serializability
-
- 06 Feb, 2004 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/mysql/mysql-4.0-merge
-