- 06 Oct, 2006 1 commit
-
-
mats@romeo.(none) authored
> sizeof(unsigned long).
-
- 05 Oct, 2006 3 commits
-
-
mats@romeo.(none) authored
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b20265-mysql-5.1-new-rpl
-
mats@romeo.(none) authored
--- BUG#20265 (Replication of CREATE-SELECT does not work correctly): Fixing bug by making binary log handle statement transactions. The binary log transaction cache can now be truncated to remove events inserted during this statement or transaction. Also, the binary log participate in XA transaction handling, although not as a full 2pc resource.
-
- 03 Oct, 2006 5 commits
-
-
-
After merge fix. field.cc: After merge fix
-
bar@bar.intranet.mysql.r18.ru authored
-
into mysql.com:/usr/home/bar/mysql-5.0-rpl
-
into mysql.com:/usr/home/bar/mysql-4.1-rpl
-
- 02 Oct, 2006 6 commits
-
-
lars/lthalmann@dl145j.mysql.com authored
into mysql.com:/users/lthalmann/bkroot/mysql-5.1-new-rpl
-
lars/lthalmann@dl145h.mysql.com authored
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge
-
into mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/fix-mysql-5.1-new-rpl
-
mats@romeo.(none) authored
Adding test case.
-
-
- 01 Oct, 2006 6 commits
-
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
brian@zim.(none) authored
This patch makes ndbcluster_hton not static. I have a second patch for ndbcluster_hton to be static, but I want to talk to Jonas first.
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/merge-5.1
-
brian@zim.(none) authored
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/arch-5.1
-
brian@zim.(none) authored
-
- 30 Sep, 2006 3 commits
-
-
brian@zim.(none) authored
This patch adds handlerton passing to functions. NDB and Innodb still require a global hanlderton in the main code due to the nature of the sql_cache call back function (should be solveable... another patch). Partitioning now has a flag to allow disabling of engines from being compatible with partitioning. Cleaned up heap naming convention on panic call.
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
brian@zim.(none) authored
-
- 29 Sep, 2006 12 commits
-
-
sergefp@mysql.com authored
-
baker@bk-internal.mysql.com authored
into bk-internal.mysql.com:/data0/bk/mysql-5.1-arch
-
sergefp@pylon.mylan authored
into mysql.com:/home/psergey/mysql-5.1-bug14940-r10a
-
sergefp@mysql.com authored
-
gkodinov@dl145s.mysql.com authored
-
sergefp@mysql.com authored
- Re-worked the prev_record_reads() function to return the lower bound of number of different table access scans that will be performed.
-
into mysql.com:/usr/home/bar/mysql-5.0.b6147rpl
-
Fix: "mysql --xml" now print NULL values the same way that "mysqldump --xml" does: <field name="name" xsi:nil="true" /> to distinguish from empty strings: <field name="name"></field> and from string "NULL": <field name="name">NULL</field>
-
Problem: for character sets having mbmaxlen==2, any ALTER TABLE changed TEXT column type to MEDIUMTEXT, due to wrong "internal length to create length" formula. Fix: removing rounding code introduced in early 4.1 time, which is not correct anymore.
-
Adding a multibyte-aware VARCHAR copying function, to put correct column prefix, taking in account number of characters (instead just limiting on number of bytes). For example, for a KEY(col(3)) on a UTF8 column when copying the string 'foo bar foo', we should put only 3 leftmost characters: 'foo'. 9 characters were incorrectly put before this fix.
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
gkodinov@dl145s.mysql.com authored
into dl145s.mysql.com:/data/bk/team_tree_merge/MERGE/mysql-5.1-opt
-
- 28 Sep, 2006 4 commits
-
-
evgen@moonbone.local authored
After merge fix
-
evgen@moonbone.local authored
into moonbone.local:/work/5505-bug-5.0-opt-mysql
-
evgen@moonbone.local authored
On an INSERT into an updatable but non-insertable view an error message was issued stating the view being not updatable. This can lead to a confusion of a user. A new error message is introduced. Is is showed when a user tries to insert into a non-insertable view.
-
brian@zim.(none) authored
into zim.(none):/home/brian/mysql/merge-5.1
-