- 01 Apr, 2004 3 commits
-
-
dlenev@jabberwock.localdomain authored
into jabberwock.localdomain:/home/dlenev/src/mysql-4.1-775
-
dlenev@jabberwock.localdomain authored
Added two status variables: binlog_cache_use - counts number of transactions that used somehow transaction temporary binary log. binlog_cache_disk_use - counts number of transactions that required disk I/O for storing info in this this binary log.
-
lenz@kallisto.local authored
distribution (this is more in line with how "make install" would install them) - this should also fix a test failure in the "system_mysql_db_fix" test.
-
- 31 Mar, 2004 9 commits
-
-
dlenev@brandersnatch.localdomain authored
-
dlenev@brandersnatch.localdomain authored
-
dlenev@brandersnatch.localdomain authored
table resolution". Added members to Item_ident for storing original db, table and field names since those that set later from Field have shorter life-time than required by prep. stmt. So we need to restore original names in Item_ident::cleanup(). Also now using special construnctor for creation of Item_field from Field object that ensures that table and field name have big enough life-time. "Fix" for bug #2050 "10 to 1 performance drop with server 4.1.1" Clean ups in implementation of caching of field number in table. Added caching of table in which field is found in find_field_in_tables().
-
gluh@gluh.mysql.r18.ru authored
into gluh.mysql.r18.ru:/home/gluh/Bugs/mysql-4.1
-
gluh@gluh.mysql.r18.ru authored
-
bell@sanja.is.com.ua authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-qc-4.1
-
jani@rhols221.adsl.netsonic.fi authored
Marked --no-set-names as deprecated, the name is misleading and --no- in front makes it cumbersome to use with --disable or --skip prefixes. The old option will still work for the time being.
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
Portability fixes
-
- 30 Mar, 2004 11 commits
-
-
konstantin@dragonfly.local authored
implemented in the client library and server. Warning: this makes the new client library and server incompatible with all previous versions and 5.0.
-
bell@sanja.is.com.ua authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
-
bar@bar.intranet.mysql.r18.ru authored
Collation gets lost in CREATE TABLE (...) DEFAULT CHARACTER SET xxx COLLATE yyy This is fixed now. Test is added into the test suite.
-
bar@bar.intranet.mysql.r18.ru authored
Forgot to do it in the previous commit.
-
bar@bar.intranet.mysql.r18.ru authored
and for (2) converting the columns: 1. ALTER TABLE t1 [DEFAULT] CHARACTER SET xxx [COLLATE yyy] 2. ALTER TABLE t1 CONVERT TO CHARACTER SET xxx [COLLATE yyy]
-
monty@mysql.com authored
-
bell@sanja.is.com.ua authored
-
ram@gw.mysql.r18.ru authored
-
ram@gw.mysql.r18.ru authored
ChangeSet 1.1707 04/03/19 12:36:55 ram@gw.mysql.r18.ru +4 -0 Fix for the bug #2976: NATURAL JOIN produces duplicate columns.
-
- 29 Mar, 2004 14 commits
-
-
monty@mysql.com authored
Fixes after last merge
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
konstantin@oak.local authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.1
-
monty@mysql.com authored
-
monty@mysql.com authored
into mysql.com:/home/my/mysql-4.0
-
bar@bar.intranet.mysql.r18.ru authored
SET character_set_xxx=NULL and SET collation_xxx=NULL
-
bar@bar.intranet.mysql.r18.ru authored
-
bar@bar.intranet.mysql.r18.ru authored
-
bar@bar.intranet.mysql.r18.ru authored
More clear error message.
-
- 28 Mar, 2004 2 commits
-
-
konstantin@mysql.com authored
No need to check for result existence any more, store_result functions now are shorter. cli_read_binary_rows rewritten to handle MYSQL_DATA directly.
-
dlenev@brandersnatch.localdomain authored
Actually it is not a bug but right behavior observed as pefomance degradation after we have forced Item_field::fix_fields() to re-execute each time when we are executing prep stmt. This patch implements small optimization which heals this bad behavior. We are caching field position in TABLE::field array in Item's member and are using this position for speeding up field lookups in fix_fields() in case of its re-execution.
-
- 27 Mar, 2004 1 commit
-
-
hf@deer.(none) authored
into deer.(none):/home/hf/work/mysql-4.1.clean
-