unknown d0d8bbed5e WL#5370 Keep forward-compatibility when changing ...

'CREATE TABLE IF NOT EXISTS ... SELECT' behaviour
BUG#47132, BUG#47442, BUG49494, BUG#23992 and BUG#48814 will disappear
automatically after the this patch.
BUG#55617 is fixed by this patch too.
            
This is the 5.5 part.
It implements:
- 'CREATE TABLE IF NOT EXISTS ... SELECT' statement will not insert
  anything and binlog anything if the table already exists.
  It only generate a warning that table already exists.
- A couple of test cases for the behavior changing.

2010-08-18 17:35:41 +08:00

..

binlog

WL#5370 Keep forward-compatibility when changing

2010-08-18 17:35:41 +08:00

bugs

Bug #49741 test files contain explicit references to bin/relay-log positions

2010-05-24 21:54:08 +08:00

engines

Manual merge

2010-05-26 22:34:25 +08:00

federated

Fix federated.federated_server.test.

2010-07-31 17:10:27 +04:00

funcs_1

merge from 5.1-bugteam of merge from 5.1-mtr

2010-08-06 13:37:05 +02:00

funcs_2

…

ibmdb2i

Unset the execute bit where it's not needed.

2010-07-03 20:17:03 -03:00

innodb

WL#5370 Keep forward-compatibility when changing

2010-08-18 17:35:41 +08:00

jp

WL#2360 Performance schema

2010-01-11 18:47:27 -07:00

large_tests

bug#50296

2010-02-28 19:39:28 +02:00

manual

Bug #49741 test files contain explicit references to bin/relay-log positions

2010-05-24 21:54:08 +08:00

ndb

Bug#49746: Const expression caching led to NDB not using engine condition

2010-08-14 13:11:33 +04:00

ndb_team

Manual merge

2010-05-26 22:34:25 +08:00

parts

Bug#49907: ALTER TABLE ... TRUNCATE PARTITION does not wait for

2010-08-16 14:53:30 +02:00

perfschema

Bug#55416 Renaming of performance_schema tables for 5.5

2010-08-12 08:08:52 -06:00

perfschema_stress

WL#2360 Performance schema

2010-01-11 18:47:27 -07:00

rpl

WL#5370 Keep forward-compatibility when changing

2010-08-18 17:35:41 +08:00

rpl_ndb

Disable rpl_ndb.rpl_ndb_row_implicit_commit_binlog due to Bug 55849.

2010-08-09 20:55:26 +04:00

stress

…

sys_vars

Change default for innodb_strict_mode to FALSE.

2010-08-13 15:07:22 -04:00