Hi!
>>>>> "Jeremy" == Jeremy Zawodny <jzawodn@stripped> writes:
<cut>
Jeremy> About a year ago, Monty mentioned having a query cache in MySQL so
Jeremy> that the really often used queries would bypass parsing and the
Jeremy> overhead there. But I don't know where that stands. I can envision a
Jeremy> MySQL add-in that we could build to handle very specific requests
Jeremy> (over a separate local socket maybe) for this particular application.
Just an update about this:
We are just about to hire a new MySQL developer; If we can just agree
on the terms, he will get the query cache as his first assignment.
Jeremy> Hmmm...
Jeremy> Now the wheels in my head are turning... :-)
Jeremy> This could be a killer feature for MySQL. The folks who always want
Jeremy> MySQL to use LDAP or some other system for authentication could just
Jeremy> build a module that does that and plug it in, right?
To replace the current authentication with LDAP, one would have to
spend at least 3-4 days to recode the current code as a replaceable
module.
It's not hard to get username, passwords and global rights from LDAP.
The problem is handling database, table and column rights in a fast
efficient manner.
Regards,
Monty
