An error occurred fetching the project authors.
- 29 Jun, 2006 17 commits
-
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-merge
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime
-
konstantin@mysql.com authored
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/main
-
konstantin@mysql.com authored
into mysql.com:/opt/local/work/mysql-5.0-runtime
-
jonas@perch.ndb.mysql.com authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-release
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0-main
-
tomas@poseidon.ndb.mysql.com authored
+ adopted signal to be as close as possible to 5.1...
-
kroki@mysql.com authored
-
jonas@perch.ndb.mysql.com authored
Fix compile error for forte
-
knielsen@mysql.com authored
into mysql.com:/data0/knielsen/tmp-5.0
-
knielsen@mysql.com authored
-
knielsen@mysql.com authored
-
- 28 Jun, 2006 23 commits
-
-
kroki@mysql.com authored
into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug10946
-
kroki@mysql.com authored
It was hard to distinguish case, when one was unable to create trigger on the table because trigger with same action time and event already existed for this table, from the case, when one tried to create trigger with name which was already occupied by some other trigger, since in both these cases we emitted ER_TRG_ALREADY_EXISTS error and message. Now we emit ER_NOT_SUPPORTED_YET error with appropriate additional message in the first case. There is no sense in introducing separate error for this situation since we plan to get rid of this limitation eventually.
-
konstantin@mysql.com authored
No test case as the bug is in an existing test case (rpl_trigger.test when it is run under valgrind). The warning was caused by memory corruption in replication slave: thd->db was pointing at a stack address that was previously used by sp_head::execute()::old_db. This happened because mysql_change_db behaved differently in replication slave and did not make a copy of the argument to assign to thd->db. The solution is to always free the old value of thd->db and allocate a new copy, regardless whether we're running in a replication slave or not.
-
patg@govinda.patg.net authored
Pushbuild fixes to result file, test, and header file for federated.
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-18005
-
patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.0-engines-bug19773
-
acurtis@xiphis.org authored
into xiphis.org:/home/antony/work2/p4-bug12096.2-merge
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
knielsen@mysql.com authored
In the Windows build files, the "Max nt" configuration for some reason had the mysql_client_test project disabled. Enable it.
-
lars@mysql.com authored
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/merge
-
knielsen@mysql.com authored
Improved definition of mysys configuration for -nt builds.
-
stewart@mysql.com authored
into mysql.com:/home/stewart/Documents/MySQL/5.0/merge
-
stewart@mysql.com authored
change default minimum to 3 bug is *very* timing dependent, unable to reproduce here, but theoretically possible.
-
tnurnberg@mysql.com authored
into mysql.com:/home/tnurnberg/mysql-5.0
-
tnurnberg@mysql.com authored
into mysql.com:/home/tnurnberg/mysql-5.0
-
tnurnberg@mysql.com authored
sp_grant_privileges(), the function that GRANTs EXECUTE + ALTER privs on a SP, did so creating a user-entry with not password; mysql_routine_grant() would then write that "change" to the user-table.
-
knielsen@mysql.com authored
Make sure for the mysys project that __NT__ is defined in *nt solution configurations (but not in other configurations).
-
aivanov@mysql.com authored
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0-kt
-
patg@govinda.patg.net authored
Final-review fixes per Monty, pre-push. OK'd for push. Please see each file's comments.
-
aivanov@mysql.com authored
into mysql.com:/home/alexi/bugs/mysql-5.0-19208
-
aivanov@mysql.com authored
and BUG#19208 "Test 'rpl000017' hangs on Windows". Both bugs are caused by attempting to delete an opened file and to create immediatedly a new one with the same name. On Windows it can be supported only on NT-platforms (by using FILE_SHARE_DELETE mode and with renaming the file before deletion). Because deleting not-closed files is not supported on all platforms (e.g. Win 98|ME) this is to be considered harmful and should be eliminated by a "code redesign".
-