I'm hardly a representative audience, statistically speaking, but I can
count on one hand the number of times I've used, or had a client use
myisampack
I've seen plenty of situations where clients SHOULD have, I'll admit
that, but the gain apparently wasn't worth whatever arbitrary cost they
assigned to the task, or they did it and a developer somewhere
complained to a sysadmin who unpacked it and left it that way because no
one noticed the difference, etc.
But I'm sitting on the "scrap" side, not because I dislike Pack (I'd
actually like GZipping fields, but thats just me), but I just don't see
enough people using it to bother maintaining it (for now, but who knows
what the future holds).
But I guess that brings up the question, is it more work to scrap it,
than to keep it.
-Daniel
Sheeri K. Cabral wrote:
Well, yes, eventually Drizzle will be all growed up and have REAL
partitioning. I'm just giving you actual use cases in the real world
these days. myisam pack is used, not very often, but when it is it
really is kinda drizzle's target market. :-\
-Sheeri
On 8/11/08, *Brian Aker* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi!
On Aug 11, 2008, at 4:44 AM, Sheeri K. Cabral wrote:
Not just needle in haystack queries, but range searches as
well. My vote is to keep, ARCHIVE is used in the real world
more for logging things which shouldn't be modified as per
compliance standards, compressed MyISAM tables are used for
things like "a list of all the cities in the world" and
"apache logs" and stuff.....mostly because MyISAM tables can
be used with MERGE.
No merge engine :)
Cheers,
-Brian
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
