From 959891662dfbb0b860f0bc70e09bc2c92dab831b Mon Sep 17 00:00:00 2001 From: Monty Date: Tue, 30 May 2017 21:31:30 +0300 Subject: MDEV-12930 Testing SEQUENCE object Fixed the following things from the above MDEV: - Ensure the user has INSERT privilege when generating new sequence values with NEXT VALUE FOR or SETVAL() - Fixed bug in InnoDB when generating several sequence values in one statement - Ensure that read_set is up to date before calling ha_sequence::ha_write_row() - This is only a potential bug with storage engines that trusts the column maps completely --- sql/ha_sequence.h | 2 ++ 1 file changed, 2 insertions(+) (limited to 'sql/ha_sequence.h') diff --git a/sql/ha_sequence.h b/sql/ha_sequence.h index 8ab452a9372..fd9da05b591 100644 --- a/sql/ha_sequence.h +++ b/sql/ha_sequence.h @@ -152,6 +152,8 @@ public: { return file->check_and_repair(thd); } bool is_crashed() const { return file->is_crashed(); } + void column_bitmaps_signal() + { return file->column_bitmaps_signal(); } /* New methods */ void register_original_handler(handler *file_arg) -- cgit v1.2.1