- 06 May, 2004 1 commit
-
-
monty@mysql.com authored
Fixed wrong key usage which caused wrong result for some "WHERE primary_key=constant" queries where MySQL could use 'only index' (Bug #3666) The bug was introduced in a patch in the 4.1.2 source tree.
-
- 05 May, 2004 22 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-ndb-4.1
-
guilhem@mysql.com authored
as the I/O thread filters on the server id, we must test replicate_same_server_id in it (on top of in the SQL thread).
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-ndb-4.1
-
bell@sanja.is.com.ua authored
SQL_SELECT_LIMIT as default will be applied only for SELECT statement if there was not explicit LIMIT clause correct table list passed to class constructor of select_update
-
monty@mysql.com authored
-
miguel@hegel.local authored
into hegel.local:/home/miguel/bk/mysql-4.1
-
miguel@hegel.local authored
-
monty@mysql.com authored
-
ram@gw.mysql.r18.ru authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
-
monty@mysql.com authored
We didn't use 'only index' for tables of type 'const'. (Bug #3497)
-
marko@hundin.mysql.fi authored
(Bug #3596)
-
marko@hundin.mysql.fi authored
-
bell@sanja.is.com.ua authored
-
marko@hundin.mysql.fi authored
into hundin.mysql.fi:/home/marko/l/mysql-4.0
-
miguel@hegel.local authored
-
- 04 May, 2004 17 commits
-
-
greg@mysql.com authored
-
Sinisa@sinisa.nasamreza.org authored
into sinisa.nasamreza.org:/mnt/work/mysql-4.1
-
Sinisa@sinisa.nasamreza.org authored
but used in a nested query.
-
dlenev@brandersnatch.localdomain authored
Now test_bug1664() uses new statement checking macros.
-
dlenev@brandersnatch.localdomain authored
-
dlenev@brandersnatch.localdomain authored
"mysql_send_long_data() API call is completely broken". Now we are resetting some members (long_data_supplied/null_value...) of Item_param to its initial state after each execution of prepared statement. We also manipulating Item_param::maybe_null/null_value only via Item_param::set_* setters which makes code a bit more robust.
-
guilhem@mysql.com authored
just for beauty of truth.
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.0
-
guilhem@mysql.com authored
in hard-coded replication messages, always put small-length info (error codes, explanation of the error) at the beginning, so that it is not cut by truncation if the query is very long (which happens if the query goes first).
-
Sinisa@sinisa.nasamreza.org authored
fixing typo union.test: fixing type
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-prep-4.1
-
bell@sanja.is.com.ua authored
-
serg@serg.mylan authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-sub-4.1
-
monty@mysql.com authored
Fixed security problem that password was temporarly reset when someone changed GRANT for a user. (Bug #3404) Fixed problem with PROCEDURE analyse() and impossible WHERE (Bug #2238) Don't auto-repair tables in mysqlcheck if table type doesn't support 'check' command.
-
Sinisa@sinisa.nasamreza.org authored
a small fix for the test case
-
joreland@mysql.com authored
Hopefully last one
-