- 21 Mar, 2005 2 commits
-
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-build
-
patg@krsna. authored
-
- 20 Mar, 2005 2 commits
-
-
dlenev@brandersnatch.localdomain authored
"Warnings on 'drop procedure' platform-specific"). In mysqltest we should not issue "SHOW WARNINGS" until we have not read results from all statements in multi-statement. Otherwise such "SHOW WARNINGS" will either cause "Packets out of order" error and thus will ruin current connection (but we may not notice this as it happened in sp.test because we ignore errors from such auxilary SHOW WARNINGS and use auto-reconnecting connections) or will succeed but consume first packet from next statement in multi-statement sequence (this happens if "SHOW WARNINGS" is issued when this packet is already received by client. Packet is thrown away by net_clear() call which is issued when "SHOW WARNINGS" is sent to server). In our case sp.test failed because usually we had first situation but sometimes second situation occured causing warning to pop-up.
-
joerg@mysql.com authored
-
- 19 Mar, 2005 5 commits
-
-
jimw@mysql.com authored
-
jimw@mysql.com authored
been killed.
-
jimw@mysql.com authored
-
jimw@mysql.com authored
(patch from lenz, reapplied by jimw)
-
jimw@mysql.com authored
Windows to call CreateFileMapping() with correct arguments, and propogating the introduction of query_id_t to everywhere query ids are passed around. (Bug #8826)
-
- 18 Mar, 2005 6 commits
-
-
kent@mysql.com authored
Disabled old feature to disable test cases
-
joerg@mysql.com authored
into mysql.com:/M50/build-5.0.3
-
joerg@mysql.com authored
-
joerg@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-build
-
jimw@mysql.com authored
-
- 17 Mar, 2005 21 commits
-
-
lenz@mysql.com authored
-
mysqldev@mysql.com authored
-
mysqldev@mysql.com authored
transactional test removed sp_trans.test, sp_trans.result: new file
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-build
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-build
-
jimw@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-build
-
lenz@mysql.com authored
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-build
-
joerg@mysql.com authored
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/MySQL-MERGE/mysql-5.0
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/MySQL-MERGE/mysql-5.0
-
serg@serg.mylan authored
into serg.mylan:/usr/home/serg/Abk/mysql-5.0
-
ramil@mysql.com authored
-
ramil@mysql.com authored
-
First one is related to Bug#7905. One should not be allowed to create new user with password without UPDATE privilege to MySQL database. Furthermore, executing the same GRANT statement twice would actually crash the server and corrupt privilege database. Other bug was that one could update a column, using the existing value as basis to calculate the new value (e.g. UPDATE t1 SET a=a+1) without SELECT privilege to the field (a in the above example) Fixed tests grant.pl and grant2, which were wrong.
-
igor@rurik.mysql.com authored
into rurik.mysql.com:/home/igor/dev/mysql-4.1-0
-
jimw@mysql.com authored
reconnect setting in mysql client library. (Bug #8866)
-
jimw@mysql.com authored
-
- 16 Mar, 2005 4 commits
-
-
igor@rurik.mysql.com authored
Added a test for bug #8615. sql_select.cc: Fixed bug #8615. This fix only removed the cause of the reported crash. It does not resolve other problems of rollup queries with DISTINCT. They were fixed in the previous patch for bug 8616.
-
monty@mysql.com authored
-
monty@mysql.com authored
Enabled VARCHAR testing for innodb NOTE: innodb.test currently fails becasue of a bug in InnoDB. I have informed Heikki about this and expect him to fix this ASAP
-
lars@mysql.com authored
-