~drizzle-trunk/drizzle/development : changes

~drizzle-trunk/drizzle/development » Changes from revision 1143.2.37

Rev	Summary	Authors	Date
1143.2.37	Merge Joe's new test cases for transaction log Merge Joe's new test cases for transaction log	Jay Pipes	15 years ago
1143.2.36	Merge trunk Merge trunk	Jay Pipes	15 years ago
1143.2.35	Adds support for BLOB fields in the replication stream. Note... Adds support for BLOB fields in the replication stream. Note that this does not yet support extremely large BLOB data. Extremely large BLOB data will be written to the transaction log in specialized transaction log entries for that. In this patch, we simply allow the main Transaction message and the reader/writer programs to work with binary data properly. Adds a simple test for BLOB fields and the transaction log. The problem was figuring out how to correctly replace embedded NUL characters in the output of the transaction reader with \\0 so that mysqltest.cc wouldn't puke when cat'ing the result of the reading of the transaction log when BLOB data was contained.	Jay Pipes	15 years ago
1143.2.34	Updated filtered_replicator test due to new tests for UPDATE... Updated filtered_replicator test due to new tests for UPDATE.	Jay Pipes	15 years ago
1143.2.33	This patch fixes a bug in the replication service and transa... 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	Merge trunk Merge trunk	Jay Pipes	15 years ago
1143.2.31	Add test case for when a transaction is manually started but... Add test case for when a transaction is manually started but no data modification occurs. This happens, for instance, when sysbench runs, and was causing major performance degradation because lots of blank transactions were being written to the transaction log needlessly.	Jay Pipes	15 years ago
1143.2.30	Mac doesn't have fdatasync() :( transaction_log.cc now uses Mac doesn't have fdatasync() :( transaction_log.cc now uses mysys/my_sync.cc's my_sync() call to handle this.	Jay Pipes	15 years ago
1143.2.29	Added fdatasync() calls to transaction_log.cc. Not sure how... Added fdatasync() calls to transaction_log.cc. Not sure how nobody caught this :)	Jay Pipes	15 years ago
1143.2.28	Moves all calls to replication services' commitNormalTransac... Moves all calls to replication services' commitNormalTransaction() into the ha_commit_one_phase() block.	Jay Pipes	15 years ago
1143.2.27	Corrects problems where REPLACE and INSERT ... ON DUPLICATE ... Corrects problems where REPLACE and INSERT ... ON DUPLICATE KEY UPDATE were not properly logging the atomic change in server state to the transaction log. The problem had to do with the log_row_for_replication() method not completely understanding whether a call to ha_update_row() had really been called during a REPLACE or INSERT call. See my blog entries for an overly-elaborate explanation as to what was really going on: http://www.jpipes.com/index.php?/archives/301-Pop-Quiz-What-Does-REPLACE-Do.html http://www.jpipes.com/index.php?/archives/303-The-Deal-with-REPLACE-..-Or-Is-It-UPDATE.html http://jpipes.com/index.php?/archives/305-Yet-Another-Post-on-REPLACE.html Added test cases for REPLACE and INSERT .. ON DUPLICATE KEY UPDATE.	Jay Pipes	15 years ago
1143.2.26	Merge trunk Merge trunk	Jay Pipes	15 years ago
1143.2.25	Merge trunk Merge trunk	Jay Pipes	15 years ago
1143.2.24	Fixes some stuff from make check (include guards). Also adds... Fixes some stuff from make check (include guards). Also adds stuff for REPLACE logic that does not work.	Jay Pipes	15 years ago
1143.2.23	Merge trunk and resolve all conflicts. Merge trunk and resolve all conflicts.	Jay Pipes	15 years ago
1143.2.22	Adds functionality to handle REPLACE statements correctly in... Adds functionality to handle REPLACE statements correctly in the replication service. REPLACE represents a DELETE of a row followed by an INSERT of new data into the same row. Adds a new test case to the transaction_log test case for REPLACE. The replace test case does not pass and I'm not sure why. Pushing up to LP so I can have krow take a looksie...	Jay Pipes	15 years ago
1143.2.21	Fixes Bug 440141 - Replication stream contains incorrect key... Fixes Bug 440141 - Replication stream contains incorrect key field information for UPDATE statements.	Jay Pipes	15 years ago
1143.2.20	* Fixes bug in replication where inserts, updates, and * Fixes bug in replication where inserts, updates, and deletes from temporary tables where being included in the replication stream. Adds a new test case for temporary table usage and the transaction log. * Fixes up all the test cases to remove the now-unecessary stripping of comments that used to be in the transaction log output from the transaction_reader program.	Jay Pipes	15 years ago
1143.2.19	Merge trunk w/ new InnoDB plugin. Merge trunk w/ new InnoDB plugin.	Jay Pipes	15 years ago
1143.2.18	Merge trunk and resolve conflicts. Merge trunk and resolve conflicts.	Jay Pipes	15 years ago

Older »