- 30 Jul, 2007 3 commits
-
-
omer@linux.site authored
into linux.site:/home/omer/source/jrg51
-
omer@linux.site authored
into linux.site:/home/omer/source/jrg51
-
joerg@trift2. authored
into trift2.:/MySQL/M51/push-5.1
-
- 27 Jul, 2007 12 commits
-
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/mysql-5.1
-
jperkin@production.mysql.com authored
into production.mysql.com:/usersnfs/jperkin/bk/bug-28585-5.1
-
df@pippilotta.erinye.com authored
-
joerg@debian.(none) authored
into debian.(none):/M51/omer-5.1
-
joerg/mysqldev@production.mysql.com authored
into mysql.com:/data0/mysqldev/my/mysql-5.1-funcs1-dep
-
into mysql.com:/data0/mysqldev/my/mysql-5.1-funcs1-dep
-
joerg@debian.(none) authored
Step 2: Restore the 5.1 contents in the 5.0-dependent files.
-
jperkin@production.mysql.com authored
- make the 'dist-hook' from top-level Makefile work again. - we can find my_print_defaults from --basedir by parsing command line arguments prior to running my_print_defaults. - take advantage of additional command line parsing and allow the --no-defaults etc arguments to work anywhere rather than having to be the first argument. - find SQL files either from binary archive or source install. - consolidate and tidy code and error messages.
-
joerg@debian.(none) authored
The files below "mysql-test/suite/funcs_1" in version 5.1 did not depend on the equivalent ones in 5.0, probably because they had been checked in independent of each other in both versions. Step 1: Foreach file F in the suite that has a "deleted" counterpart D, use bk rm $F bk mv $D $F to get those files into the 5.1 suite that (for BK) depend on 5.0.
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG29957/mysql-5.1-engines
-
svoj@june.mysql.com authored
into mysql.com:/home/svoj/devel/mysql/BUG29957/mysql-5.0-engines
-
svoj@mysql.com/june.mysql.com authored
INSERT/DELETE/UPDATE followed by ALTER TABLE within LOCK TABLES may cause table corruption on Windows. That happens because ALTER TABLE writes outdated shared state info into index file. Fixed by removing obsolete workaround. Affects MyISAM tables on Windows only.
-
- 26 Jul, 2007 19 commits
-
-
joerg@debian.(none) authored
into debian.(none):/M51/push-5.1
-
joerg@debian.(none) authored
into debian.(none):/M51/rowlock-5.1
-
joerg@debian.(none) authored
For more information, see WL#3866 and the bugs numbered 28685 and 20390.
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/anubis/antony/work/mysql-5.1-engines.merge
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/anubis/antony/work/mysql-5.1-engines.merge
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/anubis/antony/work/mysql-5.0-engines.merge
-
joerg@debian.(none) authored
into debian.(none):/M51/push-5.1
-
joerg@debian.(none) authored
into debian.(none):/M51/push-5.1
-
joerg@debian.(none) authored
into debian.(none):/M51/bug16635-5.1
-
joerg@debian.(none) authored
into debian.(none):/M50/bug16635-5.0
-
jperkin@production.mysql.com authored
Fix error in previous change, correct --language argument.
-
jperkin@production.mysql.com authored
-
jperkin@production.mysql.com authored
available and reduce the chance of failure. This should fix bug#28585 which is caused by the script being quite random in how it finds files it requires and not giving very good feedback to the user about what went wrong. Also update make_binary_distribution so that it provides the correct path to the required SQL scripts when generating mysql_install_db. The script only previously worked because of the permissive behaviour which looked around the current working directory before the "correct" location. This could lead to severe problems if the user happened to run the script from a location which contained older or even broken copies of the SQL scripts. We now require either a complete binary release (and the mysql_install_db script ran from inside the extracted archive), or an installed compiled tree, as this is the only way we can be sure everything that we need is available and ready to run. While working on this fix, also clean up the mysql_install_db script a lot to make it simpler, easier to read, and hopefully less prone to bugs in the future.
-
joerg@debian.(none) authored
to 150 or 107 characters for those messages which are generated by the embedded server during release builds. This fixes bug#16635: Error messages wrong: absolute path names, "%s" format code See the bug report or the changelog for "sql/share/english/errmsg.txt" for instructions how to do that with other languages, even at the customer site, and for the restrictions to keep.
-
antony@pcg5ppc.xiphis.org authored
into pcg5ppc.xiphis.org:/Users/antony/Work/p1-bug29522.1
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/anubis/antony/work/p2-bug25679.3.merge-5.1
-
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
- 25 Jul, 2007 6 commits
-
-
gshchepa/uchum@gleb.loc authored
Post-merge fix.
-
gshchepa/uchum@gleb.loc authored
Post-merge fix.
-
antony@pcg5ppc.xiphis.org authored
"log.cc:1448: failed assertion `mysql_bin_log.is_open() && rex_data->empty()'" When Federated's transaction support was disabled by bug29875, this assertion became unreproducable.
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.0-opt
-
gshchepa/uchum@gleb.loc authored
into gleb.loc:/home/uchum/work/bk/5.1-opt
-
acurtis/antony@ltamd64.xiphis.org authored
into xiphis.org:/anubis/antony/work/p2-bug25679.3.merge-5.1
-