summaryrefslogtreecommitdiff
path: root/sql/ha_sequence.h
diff options
context:
space:
mode:
authorMonty <monty@mariadb.org>2017-05-30 21:31:30 +0300
committerMonty <monty@mariadb.org>2017-05-30 21:31:30 +0300
commit959891662dfbb0b860f0bc70e09bc2c92dab831b (patch)
treebae0ebda5c0f26e870ea17cca6de3d92f11eae33 /sql/ha_sequence.h
parentd5d8fa6e0406b6ee1058f78ac4539eb7d0579d88 (diff)
downloadmariadb-git-959891662dfbb0b860f0bc70e09bc2c92dab831b.tar.gz
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
Diffstat (limited to 'sql/ha_sequence.h')
-rw-r--r--sql/ha_sequence.h2
1 files changed, 2 insertions, 0 deletions
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)