Hi,
Baron Schwartz wrote:
On Sun, Apr 12, 2009 at 10:23 PM, Baron Schwartz <[email protected]> wrote:
All should die - an I_S that performs is the much better interface.
Is Drizzle's I_S fast?
but really, are they fast? What are Drizzle's plans about I_S?
And the data dictionary and/or runtime memory only statistics? Both could be
useful services for any DB engine.
I'd imagine an ideal statistics module to be a memory only database engine with
UNCOMMITTED READ as the only
isolation level. It could also employ shared memory so people could write
risky but fast readonly
clients that would forgo some locking at the expense of an occasional
clientside SEGV.
Thanks,
Michael Izioumtchenko
my opinions don't necessarily coincide with those of my employer
I can't use the one in MySQL. Seriously.
It's a good way to crash a production server and cause a client to
lose a bunch of money.
If everything in Drizzle is pluggable, can SHOW commands be a plugin
that just does the translation to I_S queries for you behind the
scenes?
Doh, I should have read the rest of the thread first.
A couple of the suggestions hinted at string parsing and regexes; I
would shy away from that route if possible. I guess I just do way too
much parsing and transformation with regexes.
_______________________________________________
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
