- 28 May, 2003 3 commits
-
-
bar@bar.mysql.r18.ru authored
./configure --with-charset=latin1 --with-collation=latin1_danish_ci
-
bar@bar.mysql.r18.ru authored
ifdef wrong structure has been fixed
-
bar@bar.mysql.r18.ru authored
-
- 27 May, 2003 10 commits
-
-
bell@sanja.is.com.ua authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1
-
bell@sanja.is.com.ua authored
-
lenz@mysql.com authored
compile problems
-
monty@narttu.mysql.fi authored
Fixed new bug when reading field types
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.1
-
arjen@george.bitbike.com authored
-
vva@mysql.r18.ru authored
-
mysql@home.(none) authored
Changes according to CHARSET_INFO structure
-
mysql@home.(none) authored
utf8 was not marked as compiled
-
- 26 May, 2003 10 commits
-
-
wax@kishkin.ru authored
-
monty@narttu.mysql.fi authored
into narttu.mysql.fi:/my/mysql-4.1
-
monty@narttu.mysql.fi authored
-
monty@mashka.mysql.fi authored
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-4.1-narttu
-
heikki@hundin.mysql.fi authored
Remove accidenatlly committed debug printfs when query cache is used sql_update.cc, sql_load.cc, sql_insert.cc, sql_delete.cc: For the transactional query cache algorithm to work we must invalidate the query cache in INSERT/DELETE/UPDATE before writing to the binlog or calling ha_autocommit_... Note that binlog writing may also call commit. The crucial thing is that the transaction which modified data must not be committed BEFORE the query cache is invalidated.
-
monty@mashka.mysql.fi authored
into mashka.mysql.fi:/home/my/mysql-4.1-narttu
-
monty@mashka.mysql.fi authored
-
bar@bar.mysql.r18.ru authored
ctype_ucs2 and ctype_ujis were skipped in mistake
-
bar@bar.mysql.r18.ru authored
cp1250_czech_ci was displayed even when not compiled-in in mistake.
-
- 24 May, 2003 1 commit
-
-
mysql@home.(none) authored
Character set in this test results was displayed dispite the fact that the table has the same character set
-
- 23 May, 2003 13 commits
-
-
bar@bar.mysql.r18.ru authored
c Index.xml: Collation names form lati7 were mixed
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
Bug fix: if latin2_czech_ci is not compiled, loader din't load other latin2 collations
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
Character set is not displayed in "Type" column anymore In "Collation" column NULL instead of BINARY is now displayd for for non-character data types
-
bar@bar.mysql.r18.ru authored
into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1
-
bar@bar.mysql.r18.ru authored
Collation and coercibility tests for string functions
-
administrador@light.hegel.local authored
into light.hegel.local:C:/mysql-dev/mysql-4.1
-
administrador@light.hegel.local authored
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
USER(), DATABASE() and VERSION() return in utf8 now
-
- 22 May, 2003 3 commits
-
-
guilhem@mysql.com authored
This is because rpl_relayrotate.test uses InnoDB. Example of a failing sequence: rpl_relayrotate.test repl_user_variables.test rpl_relayrotate.test Explaination in the files. Btw all other tests which use InnoDB (innodb*.test) already have this final DROP TABLE. Removed a wrong comment of mine.
-
bar@bar.mysql.r18.ru authored
-
bar@bar.mysql.r18.ru authored
default_collation is now displayed correctly in mysqld --help mysqld --help now displays default_collation corretly, according to --default-character-set
-