{"push_id":2911232653,"size":3,"distinct_size":3,"ref":"refs/heads/2.2","head":"6e380d541b228bca95d1b607682ceb6849cd721a","before":"e73301ad718e6b5ccd571f59ccb983d1640a2fdb","commits":[{"sha":"743daa57552649ff4522437e9cf1f78c1282b325","author":{"name":"Johan Wikman","email":"493d6159e810866a8d677f030e37d296adb2f3f6@mariadb.com"},"message":"MXS-2043 Create test that exposes problem\n\nA statement like\n\n    SELECT a FROM tbl FOR UPDATE;\n\nshould be classified like QUERY_TYPE_WRITE so as to be sent\nto master.","distinct":true,"url":"https://api.github.com/repos/mariadb-corporation/MaxScale/commits/743daa57552649ff4522437e9cf1f78c1282b325"},{"sha":"2aca6226d916dd91b2fd900b6ba2035f9a7a278e","author":{"name":"Johan Wikman","email":"493d6159e810866a8d677f030e37d296adb2f3f6@mariadb.com"},"message":"MXS-2043 Classify SELECT ... FOR UPDATE as QUERY_TYPE_WRITE\n\nSELECT...FOR UPDATE locks the rows for update, but only if\nautocommit==0 or a transaction is active, so in principle even if\nit were classified as READ it'd still be sent to master when it\nactually matters.\n\nHowever, even if autocommit==1 and/or no transaction is active, a\nslave in read only mode will reject the statement if the user is\nsubject to the read only restriction (a user with super privileges\nis not), which might be considered a server bug. By classifying the\nstatement as a write, it'll be sent to master and always succeed.","distinct":true,"url":"https://api.github.com/repos/mariadb-corporation/MaxScale/commits/2aca6226d916dd91b2fd900b6ba2035f9a7a278e"},{"sha":"6e380d541b228bca95d1b607682ceb6849cd721a","author":{"name":"Johan Wikman","email":"493d6159e810866a8d677f030e37d296adb2f3f6@mariadb.com"},"message":"MXS-2043 Add system test","distinct":true,"url":"https://api.github.com/repos/mariadb-corporation/MaxScale/commits/6e380d541b228bca95d1b607682ceb6849cd721a"}]}
{"actor":{"display_login":"jhnwkmn"}}