- 28 Feb, 2005 7 commits
-
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
timour@mysql.com authored
into mysql.com:/home/timka/mysql/src/5.0-bug-8532
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
pem@mysql.comhem.se authored
a DECLARE ? HANDLER FOR stmt.
-
pem@mysql.comhem.se authored
Return false from show_binlog_events() if successful, otherwise stored procedures will think it failed.
-
timour@mysql.com authored
The problem was in that the code that analyses the applicability of the QUICK_GROUP_MIN_MAX access method for DISTINC queries assumed that there are no duplicate column references in the DISTINCT clause, and it added non-exiting key parts for the duplicate column references. The solution adds a test to check whether the select list already contained a field with the same name. If such field was already present, then it was already decided to use its key part for index access. In this such case we must skip the duplicate field instead of counting it as a new field.
-
mskold@mysql.com authored
-
- 27 Feb, 2005 3 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50-ndb
-
pekka@mysql.com authored
-
svoj@mysql.com authored
into mysql.com:/home/svoj/devel/mysql/stddev-mysql-5.0
-
- 26 Feb, 2005 6 commits
-
-
pekka@mysql.com authored
into mysql.com:/space/pekka/ndb/version/my50-ndb
-
pekka@mysql.com authored
fix error code
-
pekka@mysql.com authored
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
Temporary patch to remove some warnings
-
- 25 Feb, 2005 21 commits
-
-
heikki@hundin.mysql.fi authored
Fix wrong spelling
-
heikki@hundin.mysql.fi authored
Make InnoDB-5.0.3 to process log records of 4.1 undo log header create and reuse just like in 4.1; storing XID to the start of the undo log is a separately logged operation; this conforms to Rule 3 of InnoDB redo logging
-
svoj@mysql.com authored
This bug is also known as WL#1639.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
pem@mysql.comhem.se authored
-
monty@mysql.com authored
-
monty@mysql.com authored
(Found during build process)
-
pem@mysql.comhem.se authored
Another multi result statement added. Note: No test case, as it's not possible to get a deterministic result from this.
-
pem@mysql.com authored
into mysql.com:/home/pem/work/mysql-5.0
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb
-
pem@mysql.comhem.se authored
Have to thd->set_time() before each substatement execution, to make current_time() et al return different times within the same procedure.
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
-
joreland@mysql.com authored
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-5.0
-
joreland@mysql.com authored
into mysql.com:/home/jonas/src/mysql-4.1
-
joreland@mysql.com authored
More explicit naming of variables
-
mskold@mysql.com authored
into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb
-
- 24 Feb, 2005 3 commits
-
-
monty@mysql.com authored
Previously we only stored the first given error (the error sent to the client)
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/mysql-5.0
-
brian@zim.(none) authored
Funny sometimes how things work when in reality you would think it would crash pretty hard :)
-