There is definitely a problem with the scope of variables and status values.
The first issue is, can we create a name space that defines something that is global scope only, verses something that is per session scope. Is that possible? The second issue is then identification, you can easily change the scope of a variable within session, but you need to have multiple means of looking at it's respective values, both global and session. I'd possibly like to see a VARIABLES and STATUS table, not GLOBAL and SESSION versions. These should be columns of the table. The next issue then comes with presenting this information, a SHOW SESSION STATUS for example in the past can show GLOBAL only values making it misleading. Is there a way to label a variable/status as per session only, per global only or both. I have always found the MySQL variables and sessions very misleading at times. Fixing the namespace just in identification is a great start for the source of the variable. You now create a much bigger topic of discussion, and most likely contention. Ronald
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
