[MXS-1906]  use_sql_variables_in=master lead change user fail Created: 2018-06-07  Updated: 2020-02-17  Resolved: 2020-02-17

Status: Closed
Project: MariaDB MaxScale
Component/s: readwritesplit
Affects Version/s: 2.2.7
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: dapeng huang Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-100

 Description    

my_execute_query(mysql, "create procedure p1() select 1");
 
 my_query_and_fetch(mysql, "call p1()");
 
mysql_change_user(mysql, opt_user, opt_password, current_db);

When routing target is TARGET_MASTER; COM_CHANGE_USER will not call Backend::auth -> gw_change_user

 Comments   
Comment by markus makela [ 2018-06-21 ]

Do you have strict_sp_calls=true configured for readwritesplit? In this case it would cause these sorts of problems. With the default value of strict_sp_calls=false it should not happen.

Comment by markus makela [ 2020-02-17 ]

COM_CHANGE_USER is sent to all users even with use_sql_variables_in=master.

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