Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7105

System variable "check" and "update" functions are not called on initial value.

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: 10.0.14
        • Fix Version/s: None
        • Component/s: OTHER
        • Labels:
          None

          Description

          When declaring a GLOBAL or SESSION Variable it is possible the specify "check" and/or "update" functions enabling to check the new variable value and to execute some other actions. However, if these functions are called when using the SET command, they are not called to set the initial value coming from the cnf file or the command line.

          These functions should also be called on initial values. Not doing so is a risk to accept bad values and prevent to execute actions that can be required by the program.

          It also prevents things such as specifying a numeric value as 512M in the SET command. The variable could be declared as "string" instead of "integer" and in the "update" function it would be possible to change the representation to an integer, the same that is done when analysing the values given in cnf file.

            Gliffy Diagrams

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-7094 connect_work_size is not set properly

                • Major - Major loss of function.
                • Closed

                  Activity

                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  I don't think we can do it in 10.0. This is incompatible API change and we don't have a fine-grained version for it. If I implement what you want, I'll have to change the main plugin API version, it will invalidate all plugins

                  I'll think how to do this change in one of the future releases and also how to introduce more fine-grained versioning in this part of the API.

                  Show
                  serg Sergei Golubchik added a comment - I don't think we can do it in 10.0. This is incompatible API change and we don't have a fine-grained version for it. If I implement what you want, I'll have to change the main plugin API version, it will invalidate all plugins I'll think how to do this change in one of the future releases and also how to introduce more fine-grained versioning in this part of the API.

                    People

                    • Assignee:
                      serg Sergei Golubchik
                      Reporter:
                      bertrandop Olivier Bertrand
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated: