- 18 Jan, 2005 32 commits
-
-
bar@mysql.com authored
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/MySQL/mysql-5.0
-
gluh@gluh.mysql.r18.ru authored
-
tomas@poseidon.ndb.mysql.com authored
compile warning: changed eq_range -> eq_r
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
tomas@poseidon.ndb.mysql.com authored
-
gluh@gluh.mysql.r18.ru authored
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
sergefp@mysql.com authored
into mysql.com:/home/psergey/mysql-5.0-fix-vg1
-
guilhem@mysql.com authored
5.0 has a different way of knowing if master is < 3.23.57
-
konstantin@mysql.com authored
into mysql.com:/home/kostja/work/mysql-5.0-root
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
tomas@poseidon.ndb.mysql.com authored
-
bar@mysql.com authored
not default_charset_into. It fixes the problem that in some cases numbers where treated as CHAR(N), not as BINARY(N), e.g. wrong 'charsetnr' when sent to the client side. 2. IFNULL didn't aggregate argument charsets and collations, so IFNULL(1,'a') produced a CHAR(N). Now produces a BINARY(N). 3. SELECT PROCEDURE ANALIZE now returns BINARY columns, which is much better than it worked previously: CHAR with the default character set. But in the future it's worth to fix the fields 'Field_name' and 'Optimal_fieldtype' to use UTF8, and 'Min_value' and 'Max_value' to inherit their charsets from the original items. But it is not important, and BINARY(N) is OK for now. 4. Tests were fixed accordingly. No new tests were made, as the old onces cover everything.
-
konstantin@mysql.com authored
-
sergefp@mysql.com authored
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
tomas@poseidon.ndb.mysql.com authored
into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0
-
lenz@mysql.com authored
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-5.0-clean
-
guilhem@mysql.com authored
into mysql.com:/home/mysql_src/mysql-4.1-clean
-
bar@mysql.com authored
into mysql.com:/usr/home/bar/mysql-5.0
-
bar@mysql.com authored
We should not overwrite res if it is returned from a const item.
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
- 17 Jan, 2005 8 commits
-
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-valgrind-4.1
-
guilhem@mysql.com authored
Working around hang of master < 3.23.50 on SELECT @@unknown_var (to enable 3.23.49->4.1.10 replication)
-
reggie@bob.(none) authored
into bob.(none):/home/reggie/bk/mysql-4.1
-
reggie@bob.(none) authored
sql_lex.cc: Set query to not cacheable if we are using multistatements and there are multiple statements in this query
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1
-
paul@kite-hub.kitebird.com authored
into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-4.1
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1
-
lenz@mysql.com authored
into mysql.com:/space/my/mysql-4.1-build
-