- 12 Oct, 2005 15 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump
-
lars@mysql.com authored
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-repl
-
kent@mysql.com authored
Copy *.cnf files in mysql-test/std_data/ Makefile.am: Added std_data/*.cnf to copy ndb config
-
dlenev@mysql.com authored
into mysql.com:/home/dlenev/src/mysql-5.0-repl
-
dlenev@mysql.com authored
can't be executed on slave". It will be possible to solve this problem in more correct way when we will implement WL#2897 "Complete definer support in the stored routines".
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug13510/mysql-5.0
-
sergefp@mysql.com authored
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug13510/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug13616/mysql-5.0
-
pem@mysql.com authored
into mysql.com:/usr/home/pem/bug13616/mysql-5.0
-
gluh@mysql.com authored
into mysql.com:/home/gluh/MySQL/Merge/5.0
-
gluh@eagle.intranet.mysql.r18.ru authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0
-
gluh@mysql.com authored
-
- 11 Oct, 2005 17 commits
-
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-5.0
-
monty@mysql.com authored
- CHAR() now returns binary string as default - CHAR(X*65536+Y*256+Z) is now equal to CHAR(X,Y,Z) independent of the character set for CHAR() - Test for both ETIMEDOUT and ETIME from pthread_cond_timedwait() (Some old systems returns ETIME and it's safer to test for both values than to try to write a wrapper for each old system) - Fixed new introduced bug in NOT BETWEEN X and X - Ensure we call commit_by_xid or rollback_by_xid for all engines, even if one engine has failed - Use octet2hex() for all conversion of string to hex - Simplify and optimize code
-
evgen@moonbone.local authored
into moonbone.local:/work/13327-bug-5.0-mysql
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-5.0-build
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump
-
evgen@moonbone.local authored
into moonbone.local:/work/13327-bug-5.0-mysql
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1-build
-
lenz@mysql.com authored
-
eric@mysql.com authored
into mysql.com:/Users/eric/dev/mysql-5.0
-
jimw@mysql.com authored
into mysql.com:/home/jimw/my/mysql-5.0-clean
-
pem@mysql.com authored
Disallow conflicting use of variables named "password" and "names". If such a variable is declared, and "SET ... = ..." is used for them, an error is returned; the user must resolve the conflict by either using `var` (indicating that the local variable is set) or by renaming the variable. This is necessary since setting "password" and "names" are treated as special cases by the parser.
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0.b9278
-
bar@mysql.com authored
Fixed compilation problem on FreeBSD, after discussion with Jani. Doesn't FreeBSD follow the standard?
-
hf@deer.(none) authored
-
gluh@eagle.intranet.mysql.r18.ru authored
The fix is needed to perform locking on shared data structures This is modification of patch proposed by Leandro Santi (see http://webs.sinectis.com.ar/lesanti/misc/mysql-4.0.23a-openssl_locking.patch)
-
hf@deer.(none) authored
-
eric@mysql.com authored
-
- 10 Oct, 2005 8 commits
-
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.0
-
lars@mysql.com authored
-
svoj@mysql.com authored
into mysql.com:/home/svoj/devel/mysql/engine/mysql-5.0
-
svoj@mysql.com authored
-
svoj@mysql.com authored
-
lars@mysql.com authored
-
lars@mysql.com authored
-
lars@mysql.com authored
into mysql.com:/users/lthalmann/bk/mysql-5.0
-