Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
13.1
-
None
-
Can result in unexpected behaviour
Description
# Setup
|
CHANGE MASTER 'name' TO master_host='127.0.0.1', master_user='root'; |
SET @@SESSION.default_master_connection= 'name'; |
|
|
SET @@GLOBAL.`name`.replicate_do_db= 'named'; |
SET @@GLOBAL.``.replicate_do_db= 'unnamed'; |
|
|
SELECT @@GLOBAL.name.replicate_do_db; #=> ❌ unnamed |
SELECT @@GLOBAL.``.replicate_do_db; #=> ❌ (empty) |
|
|
# Cleanup
|
RESET SLAVE ALL; |
SET @@SESSION.default_master_connection= ''; |
SET @@GLOBAL.replicate_do_db= DEFAULT; |
I suspect this is due to the code detecting implicit @@default_master_connection checking a zero length rather than a null pointer.
Attachments
Issue Links
- relates to
-
MDEV-40296 SELECT ignores @@default_master_connection
-
- Open
-