- 18 Apr, 2007 3 commits
-
-
tomas@whalegate.ndb.mysql.com authored
- test case
-
tomas@whalegate.ndb.mysql.com authored
- both for data schema operations - also make sure schema events vet the right server id when injected into the binlog - use same mechanism to signal server_id in bug#17095, and reserve some "id's" for flagging special conditions on the event, in this case do not log it - enable printing of server ids in the testcases to show that we cot it right
-
tomas@whalegate.ndb.mysql.com authored
- make sure any value is set for linked operations as well, e.g. blob tables
-
- 17 Apr, 2007 2 commits
-
-
mats@romeo.(none) authored
compile warnings on windows machines.
-
mats@romeo.(none) authored
-
- 16 Apr, 2007 2 commits
-
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b27779-mysql-5.1-rpl
-
mats@romeo.(none) authored
-
- 13 Apr, 2007 17 commits
-
-
mats@capulet.net authored
done in previous patches. There is an error in the Sun CC compiler that treats parameters that differ in only qualifier as different, even though this is not allowed by the standard (ISO/IEC 14882:2003, Section 13.1).
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.1-rpl
-
mats@romeo.(none) authored
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.1-rpl
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b27779-mysql-5.1-rpl
-
mats@romeo.(none) authored
-
mats@romeo.(none) authored
Factoring out pack_row() and unpack_row() into new files rpl_record.{cc,h}.
-
mats@romeo.(none) authored
Updating result files with wrong server id for BEGIN and COMMIT events.
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.1-rpl
-
mats@romeo.(none) authored
configuration with HAVE_REPLICATION undefined, which causes the *_rows_log_event_old classes to only have a default constructor. This generates an error on some platforms, since the base classes does not have a default constructor defined. Updating signatures of do_prepare_row() for classes above, since signatures in base classes changed.
-
mats@romeo.(none) authored
-
mats@romeo.(none) authored
-
mats@romeo.(none) authored
into romeo.(none):/home/bkroot/mysql-5.1-rpl
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b27779-mysql-5.1-rpl
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-5.1-new-rpl
-
bar@mysql.com authored
into mysql.com:/home/bar/mysql-5.0.b20095
-
bar@mysql.com authored
Problem: single byte do_varstring1() function was called, which didn't check limit on "number of character", and checked only "number of bytes". Fix: adding a multi-byte aware function do_varstring1_mb(), to limit on "number of characters"
-
- 12 Apr, 2007 13 commits
-
-
tomas@whalegate.ndb.mysql.com authored
-
tomas@whalegate.ndb.mysql.com authored
into whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-rpl
-
tomas@whalegate.ndb.mysql.com authored
- test case - reset server id in injector
-
mats@romeo.(none) authored
Taking code from before BUG#22583 and incorporating as events to be able to read old events. Also incorporating old pack and unpack functions into patch.
-
mats@romeo.(none) authored
be skipped): Fixing test since a replace assumed that we were on slave when we were on master.
-
mats@capulet.net authored
into capulet.net:/home/bk/mysql-5.1-rpl
-
mats@capulet.net authored
-
mats@romeo.(none) authored
skipped): Post-merge changes.
-
mats@romeo.(none) authored
into romeo.(none):/home/bk/b25688-mysql-5.1-rpl
-
mats@romeo.(none) authored
into romeo.(none):/home/bkroot/mysql-5.1-rpl
-
mats@romeo.(none) authored
skipped): By moving statement end actions from Rows_log_event::do_apply_event() to Rows_log_event::do_update_pos() they will always be executed, even if Rows_log_event::do_apply_event() is skipped because the event originated at the same server. This because Rows_log_event::do_update_pos() is always executed (unless Rows_log_event::do_apply_event() failed with an error, in which case the slave stops with an error anyway). Adding test case. Fixing logic to detect if inside a group. If a rotate event occured when an initial prefix of events for a statement, but for which the table did contain a key, last_event_start_time is set to zero, causing rotate to end the group but without unlocking any tables. This left a lock hanging around, which subsequently triggered an assertion when a second attempt was made to lock the same sequence of tables. In order to solve the above problem, a new flag was added to the relay log info structure that is used to indicate that the replication thread is currently executing a statement. Using this flag, the replication thread is in a group if it is either in a statement or inside a trans- action. The patch also eliminates some gratuitous header file inclusions that were not needed (and caused compile errors) and replaced them with forward definitions.
-
bar@bar.myoffice.izhnet.ru authored
into mysql.com:/home/bar/mysql-5.1-new-rpl
-
bar@mysql.com authored
Removing wrong MYF(0) argument.
-
- 11 Apr, 2007 3 commits
-
-
mats@romeo.(none) authored
-
hakank/hakan@lu0011.wdf.sap.corp authored
-
mats@romeo.(none) authored
stopped at pos==4): Submitting patch on behalf of Andrei, who discovered the problem and provided the patch. An update of the group relay log coordinates when rotating forgot to update the group relay log name and only updated the group relay log position (and group master log name and position). This patch adds code to update the group relay log *name* as well as the position
-