By the way, by view I didn't mean a SQL view :) I was referring to his ASCII-art visual example :)
Tim On Jan 12, 2010, at 4:07 PM, Jay Pipes wrote: > ++ > > Tim Soderstrom wrote: >> Actually, I like Baron's approach by using a table-based view. I assume >> that, were this in the i_s, this would be a field I could easily filter on, >> ie: >> SELECT * FROM i_s.VARIABLES WHERE type='status' AND scope='session'; >> Or something like that. >> Tim >> On Jan 12, 2010, at 3:57 PM, Jay Pipes wrote: >>> I see what you an Jeremy mean now. Actually, this wouldn't be too much >>> trouble. In the code, the global and session variables are actually mostly >>> separate anyway (there's a bit of merge variable foo that happens, but it's >>> not too complicated). Really, what you are asking for is when *displaying* >>> the variable name, to include global and session and a dot, right? >>> >>> -jay >>> >>> Baron Schwartz wrote: >>>> Hi Tim, >>>> On Tue, Jan 12, 2010 at 4:24 PM, Tim Soderstrom >>>> <[email protected]> wrote: >>>>>> If I can further hijack the thread, the whole session -vs- global >>>>>> thing is horrible. The only real use I've seen is for things like >>>>>> per-thread buffers -- and if anything, those should be implemented as >>>>>> query hints embedded in the SQL itself. The same comment applies to >>>>>> global -vs- session status counters -- having a mixture of them come >>>>>> back from SHOW STATUS is, um, horrible. Maybe Drizzle already >>>>>> un-borked this, dunno. >>>>> I have to disagree with you there, Baron. I use per session counters >>>>> quite often as part of troubleshooting bad performance. How else do I >>>>> know if a query creates a temporary table on disk or is going a sort >>>>> merge pass? It's cake with session variables. I'd like to see these left >>>>> around myself, >>>> I want them to stay -- in fact I want MUCH more instrumentation. I'm >>>> not advocating for less. But having them be named the same thing in >>>> two scopes, with no way to know what you're getting, is a disaster. >>>> Even something this simple would be wonderful: >>>> scope name value >>>> --------- ---------- -------------- >>>> | session | Questions | 100 | >>>> | global | Questions | 1000 | >>>> Jeremy Cole had a good blog post (and bug report) on this too. >>>> Baron >>>> _______________________________________________ >>>> Mailing list: https://launchpad.net/~drizzle-discuss >>>> Post to : [email protected] >>>> Unsubscribe : https://launchpad.net/~drizzle-discuss >>>> More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
