- 08 Sep, 2004 1 commit
-
-
unknown authored
-
- 07 Sep, 2004 16 commits
-
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-4.0-0
-
unknown authored
Added newline at the end of file. mysql-test/t/select.test: Added newline at the end of file.
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
This does not fix any known bug, but is still a good idea. sql/log_event.cc: when we update thd->db in replication, it's safer to update thd->db_length too. sql/slave.cc: when we update thd->db in replication, it's safer to update thd->db_length too. sql/sql_db.cc: comment
-
unknown authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2205
-
unknown authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2205
-
unknown authored
mysql-test/r/rpl_set_charset.result: result update mysql-test/t/rpl_set_charset.test: clean up on slave too.
-
unknown authored
-
unknown authored
-
unknown authored
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
As I cannot be 100% sure that there won't be issues with some of our exotic platforms (who knows if the charset of <obscure old OS> will play fair?), I'll send an email to the build guys. Well, this holds if bk does not crash on binary chars of this cset.
-
unknown authored
into rhols221.adsl.netsonic.fi:/home/my/bk/mysql-4.0
-
unknown authored
FLOAT columns".
-
unknown authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2631
-
- 06 Sep, 2004 9 commits
-
-
unknown authored
sql/sql_table.cc: stupid me. error already exists in the function. Using a local 'int error' resulted in global 'error' not being inited, which probably made next steps (those testing global error) go wrong!
-
unknown authored
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0-opt sql/log.cc: Auto merged
-
unknown authored
sql/log.cc: removing unneeded class Disable_binlog sql/sql_class.h: removing unneeded class Disable_binlog sql/sql_table.cc: As discussed, class Disable_binlog is removed and replaced by macros.
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
unknown authored
Dependency fix. We observed that doing any change to class THD in sql_class.h resulted in mysqld going crazy (parsing errors, query cache errors in query_cache.test). This is because sql_yacc.cc depends on several .h files but those were not listed in the dependencies of sql_yacc.o. The present patch does fix the issue; but my auto*-expert colleagues may have a better one. sql/Makefile.am: sql_yacc.c includes mysql_priv.h, slave.h etc, so sql_yacc.o does depend on these .h files; so they need to be listed in the dependencies.
-
unknown authored
myisammrg/myrg_open.c: backport from 4.1 mysql-test/r/union.result: after merge fix mysql-test/t/union.test: after merge fix sql/log.cc: backward compatibility: inhibit severity labels in error log
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0 mysql-test/r/union.result: Auto merged mysql-test/t/union.test: Auto merged
-
unknown authored
(Jani's CS 1.1675 04/01/05 21:45:14 was adapted an aplied). client/mysql.cc: A fix (bug #2205 USE database doesn't work after DROP database + CREATE database).
-
- 05 Sep, 2004 1 commit
-
-
unknown authored
BitKeeper/etc/ignore: Added support-files/my-innodb-heavy-4G.cnf to the ignore list mysql-test/r/union.result: drop table added mysql-test/t/union.test: drop table added
-
- 03 Sep, 2004 5 commits
-
-
unknown authored
Allow FROM or IN in SHOW KEYS, as in other SHOW statements. sql/sql_yacc.yy: Allow FROM or IN in SHOW KEYS, as in other SHOW statements.
-
unknown authored
-
unknown authored
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-4.0-0 sql/sql_select.cc: Auto merged
-
unknown authored
Added a test case for bug #5333. null_key.result, key_primary.result: Made covering index usable for const tables. sql_select.cc: Made covering index usable for const tables: downported the corresponding code from 4.1. Simultaneously fixed bug #5333 reported for 4.1. The bug was due to the fact that field index in join structures was always set to 0 for const tables. sql/sql_select.cc: Made covering index usable for const tables: downported the corresponding code from 4.1. Simultaneously fixed bug #5333 reported for 4.1. The bug was due to the fact that field index in join structures was always set to 0 for const tables. mysql-test/t/select.test: Added a test case for bug #5333. mysql-test/r/key_primary.result: Made covering index usable for const tables. mysql-test/r/null_key.result: Made covering index usable for const tables. mysql-test/r/select.result: Added a test case for bug #5333.
-
- 02 Sep, 2004 3 commits
-
-
unknown authored
Add GPL comment sql/share/czech/errmsg.txt: Add GPL comment sql/share/danish/errmsg.txt: Add GPL comment sql/share/dutch/errmsg.txt: Add GPL comment sql/share/english/errmsg.txt: Add GPL comment sql/share/estonian/errmsg.txt: Add GPL comment sql/share/french/errmsg.txt: Add GPL comment sql/share/german/errmsg.txt: Add GPL comment sql/share/greek/errmsg.txt: Add GPL comment sql/share/hungarian/errmsg.txt: Add GPL comment sql/share/italian/errmsg.txt: Add GPL comment sql/share/japanese/errmsg.txt: Add GPL comment sql/share/korean/errmsg.txt: Add GPL comment sql/share/norwegian-ny/errmsg.txt: Add GPL comment sql/share/norwegian/errmsg.txt: Add GPL comment sql/share/polish/errmsg.txt: Add GPL comment sql/share/portuguese/errmsg.txt: Add GPL comment sql/share/romanian/errmsg.txt: Add GPL comment sql/share/russian/errmsg.txt: Add GPL comment sql/share/slovak/errmsg.txt: Add GPL comment sql/share/spanish/errmsg.txt: Add GPL comment sql/share/swedish/errmsg.txt: Add GPL comment sql/share/ukrainian/errmsg.txt: Add GPL comment
-
unknown authored
into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5232
-
unknown authored
-
- 01 Sep, 2004 5 commits
-
-
unknown authored
-
unknown authored
into mysql.com:/space/my/mysql-4.0
-
unknown authored
into mysql.com:/space/my/mysql-4.0-build
-
unknown authored
BitKeeper/deleted/.del-errmsg.OLD~de59ad17392012d: Delete: sql/share/swedish/errmsg.OLD
-
unknown authored
If ALTER TABLE ... DROP FOREIGN KEY ... fails because of a wrong constraint name, return a table handler error number 150 instead of 152; the value 152 was misleading, as it referred to '152 = Cannot delete a parent row', whereas '150 = Foreign key constraint is incorrectly formed' is less misleading sql/ha_innodb.cc: If ALTER TABLE ... DROP FOREIGN KEY ... fails because of a wrong constraint name, return a table handler error number 150 instead of 152; the value 152 was misleading, as it referred to '152 = Cannot delete a parent row', whereas '150 = Foreign key constraint is incorrectly formed' is less misleading
-