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 chan
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 wo
++
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
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 wrot
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 *display
On Jan 12, 2010, at 3:30 PM, Baron Schwartz wrote:
> Hi Tim,
>
> On Tue, Jan 12, 2010 at 4:24 PM, Tim Soderstrom
> 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
Hi Tim,
On Tue, Jan 12, 2010 at 4:24 PM, Tim Soderstrom
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 embedde
Hi Tim,
> 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?
I think the specific problem baron was talking about was ambi
On Jan 12, 2010, at 3:18 PM, Baron Schwartz wrote:
> Hi,
>
> On Tue, Jan 12, 2010 at 1:32 AM, Morgan Tocker wrote:
>>> key_buffer_size => myisam_key_cache_size
>>> key_cache_block_size => myisam_key_cache_block_size
>>> key_cache_division_limit => myisam_key_cache_division_limit
>>> key_cache_a
Hi,
On Tue, Jan 12, 2010 at 1:32 AM, Morgan Tocker wrote:
>> key_buffer_size => myisam_key_cache_size
>> key_cache_block_size => myisam_key_cache_block_size
>> key_cache_division_limit => myisam_key_cache_division_limit
>> key_cache_age_threshold => myisam_key_cache_age_threshold
>
> ++
>
> This
Morgan Tocker wrote:
Hi Jay,
key_buffer_size => myisam_key_cache_size
key_cache_block_size => myisam_key_cache_block_size
key_cache_division_limit => myisam_key_cache_division_limit
key_cache_age_threshold => myisam_key_cache_age_threshold
++
This might not be the right thread to hijack, but
Hi Jay,
> key_buffer_size => myisam_key_cache_size
> key_cache_block_size => myisam_key_cache_block_size
> key_cache_division_limit => myisam_key_cache_division_limit
> key_cache_age_threshold => myisam_key_cache_age_threshold
++
This might not be the right thread to hijack, but is there any
pro
On Mon, Jan 11, 2010 at 01:25:34PM -0500, Jay Pipes wrote:
> key_buffer_size => myisam_key_cache_size
> key_cache_block_size => myisam_key_cache_block_size
> key_cache_division_limit => myisam_key_cache_division_limit
> key_cache_age_threshold => myisam_key_cache_age_threshold
>
> Let me know if t
++
On Mon, Jan 11, 2010 at 7:25 PM, Jay Pipes wrote:
> Hi all!
>
> Yesterday evening I hacked up some changes to get rid of some global server
> variables that only related to MyISAM and putting those server variables
> into the MyISAM plugin's namespace.
>
> As you may or may not know, server va
Tim Soderstrom wrote:
On Jan 11, 2010, at 12:48 PM, Rob Wultsch wrote:
On Mon, Jan 11, 2010 at 11:25 AM, Jay Pipes wrote:
Hi all!
Yesterday evening I hacked up some changes to get rid of some global server
variables that only related to MyISAM and putting those server variables
into the MyIS
Rob Wultsch wrote:
>
> This isn't OK. This is great. The semi-generalized sounding names for
> myisam variables is a footgun.
>
++
___
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe
On Jan 11, 2010, at 12:48 PM, Rob Wultsch wrote:
> On Mon, Jan 11, 2010 at 11:25 AM, Jay Pipes wrote:
>> Hi all!
>>
>> Yesterday evening I hacked up some changes to get rid of some global server
>> variables that only related to MyISAM and putting those server variables
>> into the MyISAM plugi
On Mon, Jan 11, 2010 at 11:25 AM, Jay Pipes wrote:
> Hi all!
>
> Yesterday evening I hacked up some changes to get rid of some global server
> variables that only related to MyISAM and putting those server variables
> into the MyISAM plugin's namespace.
>
> As you may or may not know, server varia
Hi all!
Yesterday evening I hacked up some changes to get rid of some global
server variables that only related to MyISAM and putting those server
variables into the MyISAM plugin's namespace.
As you may or may not know, server variables in a plugin's namespace are
automatically prefixed wit
19 matches
Mail list logo
