1143.3.7
|
|
|
Jay Pipes |
14 years ago
|
|
|
1143.3.6
|
|
|
Jay Pipes |
14 years ago
|
|
|
1143.3.5
|
|
|
Jay Pipes |
14 years ago
|
|
|
1143.3.4
|
|
|
Jay Pipes |
14 years ago
|
|
|
1143.3.3
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.3.2
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.3.1
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.35
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.34
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.33
|
|
This patch fixes a bug in the replication service and transaction proto file that was occurring when an UPDATE statement was SETting a field to a value by referencing the field itself.
For instance, imagine the following scenario:
CREATE TABLE t1 (id INT NOT NULL PRIMARY KEY, count INT NOT NULL); INSERT INTO t1 (id, counter) VALUES (1,1),(2,2),(3,3); UPDATE t1 SET counter = counter + 1 WHERE id IN (1,2);
Previously, the UpdateHeader message contained a single set_value byte array containing the new value to set the field to. However, in scenarios such as the above, for each record being updated, the value that the field would be set to is different. Therefore, this patch moves the set_value byte array from the UpdateHeader message into the UpdateRecord message and names it after_value to match the existing before_value byte array.
This patch adds a test case to the existing update.test case in the transaction log suite and modifies the statement_transform library to properly handle the above scenario.
|
Jay Pipes |
15 years ago
|
|
|
1143.2.32
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.31
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.30
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.29
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.28
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.27
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.26
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.25
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.24
|
|
|
Jay Pipes |
15 years ago
|
|
|
1143.2.23
|
|
|
Jay Pipes |
15 years ago
|
|
|