- 07 Oct, 2004 16 commits
-
-
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
-
joerg@mysql.com authored
function being used before it was defined - "forward" declaration was insufficient.
-
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
-
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 7 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
-
tomas@poseidon.ndb.mysql.com authored
and testcases
-
ram@gw.mysql.r18.ru authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5733
-
- 05 Oct, 2004 17 commits
-
-
brian@brian-akers-computer.local authored
into brian-akers-computer.local:/Users/brian/mysql/mysql-4.1
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
monty@mysql.com authored
Cleaned up patch for checking locks for multi-table updates
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-4.1-bf
-
dlenev@brandersnatch.localdomain authored
introduced during implementation of TIMESTAMP columns, which are able to store NULLs (Unfortunately it is impossible to write test case for this. Kudos to Holyfoot for noticing it!)
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.5730
-
bar@mysql.com authored
-
heikki@hundin.mysql.fi authored
Fix typos in previous push
-
heikki@hundin.mysql.fi authored
into hundin.mysql.fi:/home/heikki/mysql-4.1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.0
-
hf@deer.(none) authored
Recusive part leads to stack overflow
-
tomas@poseidon.ndb.mysql.com authored
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/k/mysql-4.0
-
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.
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/j/mysql-4.1
-
gluh@gluh.mysql.r18.ru authored
-