[MDEV-23135] System variable session_track_user_variables isn't documented Created: 2020-07-09  Updated: 2020-07-11

Status: Open
Project: MariaDB Server
Component/s: Documentation
Affects Version/s: 10.5
Fix Version/s: 10.5

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Ian Gilfillan
Resolution: Unresolved Votes: 0
Labels: None


 Description    

MariaDB [test]> select * from information_schema.system_variables where variable_name = 'session_track_user_variables' \G
 
*************************** 1. row ***************************
 
        VARIABLE_NAME: SESSION_TRACK_USER_VARIABLES
 
        SESSION_VALUE: OFF
 
         GLOBAL_VALUE: OFF
 
  GLOBAL_VALUE_ORIGIN: COMPILE-TIME
 
        DEFAULT_VALUE: OFF
 
       VARIABLE_SCOPE: SESSION
 
        VARIABLE_TYPE: BOOLEAN
 
     VARIABLE_COMMENT: Track changes to user variables.
 
    NUMERIC_MIN_VALUE: NULL
 
    NUMERIC_MAX_VALUE: NULL
 
   NUMERIC_BLOCK_SIZE: NULL
 
      ENUM_VALUE_LIST: OFF,ON
 
            READ_ONLY: NO
 
COMMAND_LINE_ARGUMENT: OPTIONAL
 
    GLOBAL_VALUE_PATH: NULL
 
1 row in set (0.006 sec)

I couldn't find anything in the KB.

 Comments   
Comment by Ian Gilfillan [ 2020-07-11 ]

Is this meant to be in 10.5? I don't see it in my 10.5.4, and I see MDEV-16470 targeted for 10.6

Comment by Elena Stepanova [ 2020-07-11 ]

MDEV-16470 has a messy history, it shouldn't have been re-opened and re-targeted for 10.6 after it had been pushed into 10.5.0. It's become really confusing.
It also doesn't help that MDEV-22574 was pushed with a commit message pointing at MDEV-16470.

So, we now have a commit for MDEV-16470 in 10.5.0+, another commit for MDEV-16470 in 10.5.4+, and the item is still open.
sanja, can you sort it out? I think MDEV-16470 should be re-closed properly. And another item should be created instead for whatever is planned to be done in 10.6.

Generated at Thu Feb 08 09:20:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.