An error occurred fetching the project authors.
- 11 Aug, 2006 3 commits
-
-
justin.he@qa3-104.qa.cn.tlan authored
-
justin.he@qa3-104.qa.cn.tlan authored
into qa3-104.qa.cn.tlan:/mnt/sda7/justin.he/mysql/mysql-5.1-ndb-bj
-
justin.he@qa3-104.qa.cn.tlan authored
use correct termninology
-
- 10 Aug, 2006 10 commits
-
-
pgalbraith/patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.1-engines-merge
-
patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.1-engines-merge
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-runtine-merge
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/m51
-
andrey@example.com authored
how did it get in?!? (it's only in local csets so no other tree is affected)
-
andrey@example.com authored
-
serg@janus.mylan authored
into janus.mylan:/usr/home/serg/Abk/m51
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
- 09 Aug, 2006 6 commits
-
-
evgen@moonbone.local authored
After merge fix
-
andrey@lmy004. authored
into lmy004.:/work/mysql-5.1-runtime
-
andrey@lmy004. authored
create function func() returns char(10) binary ... is no more possible. This will be reenabled when bug 2676 "DECLARE can't have COLLATE clause in stored procedure" is fixed. Fix after 2nd review
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-rt-merge
-
kroki/tomash@moonlight.intranet authored
-
kroki/tomash@moonlight.intranet authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-merge
-
- 08 Aug, 2006 5 commits
-
-
evgen@sunlight.local authored
into sunlight.local:/local_work/leak_fix-5.1-mysql
-
patg@govinda.patg.net authored
(this is not a fix to the bug, but simply to disable the test in order to push a 5.0 to 5.1 merge) This merge contains: Push by holyfoot@production.mysql.com on Tue Jul 25 13:41:40 2006: bk clone -l -r'holyfoot/hf@mysql.com/deer.(none)|ChangeSet|20060725085017|41021' mysql-5.0 tmp_merge
-
evgen@sunlight.local authored
Correct memory leak fix
-
patg@govinda.patg.net authored
into govinda.patg.net:/home/patg/mysql-build/mysql-5.1-5.0-merge2 Push by holyfoot@production.mysql.com on Tue Jul 25 13:41:40 2006: bk clone -l -r'holyfoot/hf@mysql.com/deer.(none)|ChangeSet|20060725085017|41021' mysql-5.0 tmp_merge
-
petr/cps@mysql.com/owlet. authored
we didn't check for NULL value of the lex_create_info->db_type pointer. The pointer is NULL in the case, when the engine name is unknown to the server. This happens with NDB on Windows.
-
- 04 Aug, 2006 2 commits
-
-
andrey@lmy004. authored
The following procedure was not possible if max_sp_recursion_depth is 0 create procedure show_proc() show create procedure show_proc; Actually there is no recursive call but the limit is checked. Solved by temporarily increasing the thread's limit just before the fetch from cache and decreasing after that.
-
petr/cps@owlet. authored
into mysql.com:/home/cps/mysql/devel/5.1-curs-bug
-
- 03 Aug, 2006 14 commits
-
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/mrg51-c
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
jimw@rama.(none) authored
into rama.(none):/home/jimw/my/mysql-5.1-clean
-
tsmith@maint1.mysql.com authored
-
msvensson@neptunus.(none) authored
Use "--source" command instead of "source", makes mysql-test-run.pl dtecte this as test case that need binlog format row.
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/mrg51-c
-
petr/cps@mysql.com/owlet. authored
gets deadlocked when dropping w/ log on" Log tables rely on concurrent insert machinery to add data. This means that log tables are always opened and locked by special (artificial) logger threads. Because of this, the thread which tries to drop a log table starts to wait for the table to be unlocked. Which will happen only if the log table is disabled. Alike situation happens if one tries to alter a log table. However in addition to the problem above, alter table calls check_if_locking_is_allowed() routine for the engine. The routine does not allow alter for the log tables. So, alter doesn't start waiting forever for logs to be disabled, but returns with an error. Another problem is that not all engines could be used for the log tables. That's because they need concurrent insert. In this patch we: (1) Explicitly disallow to drop/alter a log table if it is currently used by the logger. (2) Update MyISAM to support log tables (3) Allow to drop log tables/alter log tables if log is disabled At the same time we (4) Disallow to alter log tables to unsupported engine (after this patch CSV and MyISAM are alowed) Recommit with review fixes.
-
tsmith@maint1.mysql.com authored
-
msvensson@neptunus.(none) authored
-
msvensson@neptunus.(none) authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint
-
petr/cps@mysql.com/owlet. authored
Due to incorrect handling of FLUSH TABLES, log tables were marked for flush, but not reopened. Later we started to wait for the log table to be closed (disabled) after the flush. And as nobody disabled logs in concurrent treads, the command lasted forever. After internal consultations it was decided to skip logs during FLUSH TABLES. The reasoning is that logging is done in the "log device", whatever it is which is always active and controlled by FLUSH LOGS. So, to flush logs one should use FLUSH LOGS, and not FLUSH TABLES.
-
tsmith@maint1.mysql.com authored
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/mrg51-c
-
tsmith@maint1.mysql.com authored
into maint1.mysql.com:/data/localhome/tsmith/bk/mrg51-b
-