[MXS-1584] Add SEQUENCE support Created: 2017-12-19  Updated: 2018-10-04  Resolved: 2018-01-04

Status: Closed
Project: MariaDB MaxScale
Component/s: qc_sqlite
Affects Version/s: 2.2.0, 2.2.1
Fix Version/s: 2.2.1

Type: New Feature Priority: Major
Reporter: markus makela Assignee: Johan Wikman
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-2080 In SQL_MODE=ORACLE, sequence_name.nex... Closed
Sprint: 2017-49

 Description   

The following is an excerpt from a MaxScale log.

2017-12-19 19:00:10   info   : (6) [readwritesplit] > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, type: QUERY_TYPE_READ, stmt: select next value for seq1 
2017-12-19 19:00:10   info   : (6) [readwritesplit] Route query to slave        [192.168.121.95]:3306 <
2017-12-19 19:00:53   info   : (6) [readwritesplit] > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, type: QUERY_TYPE_READ|QUERY_TYPE_WRITE, stmt: select nextval(seq1) 
2017-12-19 19:00:53   info   : (6) [readwritesplit] Route query to master       [192.168.121.57]:3306 <
2017-12-19 19:03:30   info   : (6) [readwritesplit] > Autocommit: [enabled], trx is [not open], cmd: (0x03) COM_QUERY, type: QUERY_TYPE_READ, stmt: select seq1.nextval 
2017-12-19 19:03:30   info   : (6) [readwritesplit] Route query to slave        [192.168.121.95]:3306 <

It shows that the logically equivalent statements are not handled in a consistent way. All of the statements should be classified as reads that must be sent to the master, the same way that @@last_insert_id is treated.


Generated at Thu Feb 08 04:07:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.