diff options
| author | Vicențiu Ciorbaru <vicentiu@mariadb.org> | 2015-05-29 17:19:53 +0300 |
|---|---|---|
| committer | Vicențiu Ciorbaru <vicentiu@mariadb.org> | 2015-06-22 10:35:48 +0300 |
| commit | d1634c66ea85a7388ac54799613feb30e8733848 (patch) | |
| tree | a9fee95a6fc87b96c27f303fe9119d9b3904dd51 /sql/table.cc | |
| parent | 563e35ad27ac315548e47b40c72b5ec2e4bc9250 (diff) | |
| download | mariadb-git-bb-10.1-binlog_row_image.tar.gz | |
[MDEV-6877] Change replication event loop to account for empty eventsbb-10.1-binlog_row_image
When writing rows with a minimal row image, it is possible to receive
empty events. In that case m_curr_row and m_rows_end are the same,
however the event implies an insert into the table with the default
values associated for that table.
Diffstat (limited to 'sql/table.cc')
| -rw-r--r-- | sql/table.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sql/table.cc b/sql/table.cc index 7a1248b4144..9df5b05c04d 100644 --- a/sql/table.cc +++ b/sql/table.cc @@ -5975,7 +5975,7 @@ void TABLE::mark_columns_needed_for_insert() the read_set at binlogging time (for those cases that we only want to log a PK and we needed other fields for execution). - */ +*/ void TABLE::mark_columns_per_binlog_row_image() { DBUG_ENTER("mark_columns_per_binlog_row_image"); |