mariadb/mysql-test/suite
unknown af9f7a239e re-push of Bug 29536 for 5.1.22: timestamp inconsistent in replication around 1970
MySQL replicates the time zone only when operations that involve
it are performed. This is controlled by a flag. But this flag
is set only on successful operation.
The flag must be set also when there is an error that involves
a timezone (so the master would replicate the error to the slaves).


mysql-test/suite/rpl/r/rpl_timezone.result:
  repush of Bug 29536 for 5.1.22 tree: test case
mysql-test/suite/rpl/t/rpl_timezone.test:
  repush of Bug 29536 for 5.1.22 tree: test case
sql/field.cc:
  re-push of Bug 29536 for 5.1.22: move setting of the flag before the operation
  (so it apples to errors as well).
sql/time.cc:
  re-push of Bug 29536 for 5.1.22: move setting of the flag before the operation
  (so it apples to errors as well).
2007-08-27 12:33:57 +03:00
..
binlog Merge mysql_cab_desk.:C:/source/c++/mysql-5.1 2007-08-02 15:27:47 -04:00
funcs_1 Updated funcs_1 test and result files (not including cluster) for 5.1.21 2007-08-06 18:46:00 -07:00
funcs_2 WL#3933 Split main test suite to rpl, rpl_ndb and ndb 2007-06-27 14:28:02 +02:00
jp Many files: 2005-01-07 14:32:05 +02:00
large_tests Bug#27029 alter table ... enable keys crashes mysqld on large table 2007-06-21 12:45:56 -04:00
ndb unable to reproduce bug, perhaps pushbuild can give more info 2007-08-24 09:50:54 +02:00
parts Merge chilla.local:/home/mydev/mysql-5.1-amain 2007-07-14 19:35:43 +02:00
rpl re-push of Bug 29536 for 5.1.22: timestamp inconsistent in replication around 1970 2007-08-27 12:33:57 +03:00
rpl_ndb WL#3228 (NDB) : RBR using different table defs on slave/master 2007-07-29 18:10:42 -04:00
stress Additional tests checking for symptoms observed within 2007-07-13 18:32:22 +02:00