- 07 Oct, 2004 29 commits
-
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-ndb-merge
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
...
-
tomas@poseidon.ndb.mysql.com authored
-
magnus@neptunus.(none) authored
into neptunus.(none):/home/magnus/mysql/mysql-4.1-ndb
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-ndb
-
heikki@hundin.mysql.fi authored
Merge manually the InnoDB mysqldump -l crash patch (crash with LOCK TABLES ... LOCAL) from 4.0 to 4.1; some code cleanup
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
magnus@neptunus.(none) authored
-
joerg@mysql.com authored
function being used before it was defined - "forward" declaration was insufficient.
-
magnus@neptunus.(none) authored
Initialise "sorted" variable in constructor of QUICK_SELECT. The variable is set to 1 in test_if_skip_sort_order if we decide to optimize "order by" by uinsg index_read.
-
magnus@neptunus.(none) authored
into neptunus.(none):/home/magnus/mysql/mysql-4.1-ndb
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-ndb
-
monty@mysql.com authored
-
dlenev@mysql.com authored
differently when converting column to auto_increment in 4.1" with current tree.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
dlenev@brandersnatch.localdomain authored
to auto_increment in 4.1". Now we are enforcing NO_AUTO_VALUE_ON_ZERO mode during ALTER TABLE only if we are converting one auto_increment column to another auto_increment column (this also includes most common case when we don't do anything with such column). Also now when we convert some column to TIMESTAMP NOT NULL column with ALTER TABLE we convert NULL values to current timestamp, (as we do this in INSERT). One can still get old behavior by setting system TIMESTAMP variable to 0.
-
brian@brian-akers-computer.local authored
into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
-
monty@mysql.com authored
Some bigger code changes was necessary becasue of the multi-table-update and the new HANDLER code
-
magnus@neptunus.(none) authored
-
magnus@neptunus.(none) authored
-
brian@brian-akers-computer.local authored
Clean up from Bar and Antony code review. Found an issue with the header file were it could end up corrupted.
-
- 06 Oct, 2004 11 commits
-
-
rburnett@build.mysql.com authored
into build.mysql.com:/users/rburnett/mysql-4.0
-
rburnett@build.mysql.com authored
mysqld.cc: Added call to create_pid_file to start_signal_handler on windows. Also removed the #ifndef WINDOWS from two calls that deletes the pid file
-
monty@mysql.com authored
Noteworthy: - New HANDLER code - New multi-update-grant-check code - Table lock code in ha_innodb.cc was not applied
-
monty@mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-ndb2
-
tomas@poseidon.ndb.mysql.com authored
fix for compile error in gcc.3.4.4 and run error in gcc3.3.2
-
tomas@poseidon.ndb.mysql.com authored
-
tomas@poseidon.ndb.mysql.com authored
and testcases
-
joreland@mysql.com authored
fix of changed clo to mysql-test-run
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5733
-
joreland@mysql.com authored
-