- 04 Feb, 2004 1 commit
-
-
monty@mysql.com authored
-
- 03 Feb, 2004 10 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
-
serg@serg.mylan authored
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2185
-
monty@mysql.com authored
Now one need only SELECT privilege for tables that are only read in UPDATE statements with many tables. (Bug #2377).
-
jani@ua141d10.elisa.omakaista.fi authored
Marked --bdb-no-sync as deprecated Added --sync-bdb-logs / --disable-sync-bdb-logs as a synonym / alternative.
-
ram@gw.mysql.r18.ru authored
-
bar@bar.intranet.mysql.r18.ru authored
-
monty@mysql.com authored
Give error if locked table is used twice in query. This fixes strange error message when doing LOCK TABLES t1 WRITE; INSERT TABLE t1 SELECT * from t1 (Bug #2296)
-
- 02 Feb, 2004 5 commits
-
-
konstantin@mysql.com authored
"system variable query_prealloc_size can be only global"
-
serg@serg.mylan authored
increase the size of a signal thread's stack (the old one was too small for the thread to be created on some systems) bug#2599
-
serg@serg.mylan authored
-
ram@gw.mysql.r18.ru authored
thnx Paul. <monty> can you get the above into configure and make Makefile.am patch mysql.server.sh with the right values for mysql.server ? <monty> or do you think we should just put the above in mysql.server.sh directly <ramil> as you want <monty> the last is kind of hard to do with variables, so lets put the above in mysql.server.sh directly
-
salle@vafla.home authored
s/expection/exception
-
- 01 Feb, 2004 6 commits
-
-
heikki@hundin.mysql.fi authored
Change tests so that tables are dropped in an order respecting the FOREIGN KEY constraints
-
heikki@hundin.mysql.fi authored
Change tests so that tables are dropped in an order respecting the FOREIGN KEY constraints
-
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
-
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
-
heikki@hundin.mysql.fi authored
Cleanup
-
- 30 Jan, 2004 5 commits
-
-
dlenev@mysql.com authored
Moved all range checks for TIMESTAMP value to my_gmt_sec(). Also fixed check of upper boundary of TIMESTAMP range (which also now will catch datetime values which are too small for TIMESTAMP in case if time_t is unsigned).
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.0-bg2464
-
dlenev@mysql.com authored
values for TIMESTAMP columns. The solution is not perfect since we just silently ignoring default value for first TIMESTAMP column and properly reflecting this fact in SHOW CREATE TABLE. We can't give a warning or simply support standard syntax (niladic functions as legal value for default) for first field since it is 4.0 tree.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
Fixed parsing of column names and foreign key constraints in Innobase to handle quoted identifiers and identifiers with space. (Bug #1725) Fix optimizer tuning bug when first used key part was a constant. (Bug #1679)
-
- 29 Jan, 2004 5 commits
-
-
guilhem@mysql.com authored
when we open the HEAP table for the first time since server restart, in hp_open(), we set a flag to propagate this info to the handler level which then writes a DELETE FROM this_heap_table to the binlog. It is not a perfect solution for the bug, because between the server start and the first open of the table, the slave still had old data in his table so a SELECT on the slave may show wrong content. But if there is a --init-file to populate the HEAP table on master as startup, then this is a safe fix (I'll put a note about init-file in the HEAP section of the manual).
-
guilhem@mysql.com authored
(as long as replicate-*-table rules were defined, multi-table DELETE was never replicated by the slave).
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
This fixed problem with index reads on character fields with BDB tables. (Bug #2509)
-
heikki@hundin.mysql.fi authored
Fix bug: InnoDB row count and index cardinality estimates wrapped over at 512 million in 32-bit computers
-
- 28 Jan, 2004 2 commits
-
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
reset errors (in thd) before executing the event. Otherwise if an event is ignored because of replicate-*-table rules (error ER_SLAVE_IGNORED_TABLE) this error code may remain in thd->net and the next event may pick it.
-
- 27 Jan, 2004 1 commit
-
-
heikki@hundin.mysql.fi authored
Fix bug #2483 with InnoDB, UNIQUE secondary index, and NULL values in that unique index; with the IS NULL predicate, InnoDB returned only the first matching row, though there can be many
-
- 22 Jan, 2004 5 commits
-
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2298
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
into eagle.mysql.r18.ru:/home/vva/work/BUG_2290/mysql-4.0
-
vva@eagle.mysql.r18.ru authored
-
ram@gw.mysql.r18.ru authored
<monty> ramil, in MySQL/MyISAM we should only strip end space, not 'space-like' characters. <monty> This is according to SQL; When doing a comparision end space and only end space are ignored.
-