Search.pm SQL queries

[Max Kanat-Alexander]

On Thu, 26 Feb 2009 12:24:18 -0800 David Marshall
<dmarshal at yahoo-inc.com> wrote:
> The greater likelihood for this summer is that we'll be able to throw
> some code out as inspiration for others to make patches, but barring
> that, I'll eventually produce patches myself.

	Cool. Throwing out some code is at least better than
nothing. :-) Historically it doesn't have much effect, though.

> Too much secret MySQL sauce for this to be a realistic possibility.

	You mean in the queries you're generating? I was mostly just
curious if the query planner does better.

> We're moving some of our shadow databases to MySQL 5.1 very soon to
> see what happens.  My only concern is whether "improving" queries for
> 4.1 will actually be counterproductive in 5.1.  I see a lot of
> slow-query log browsing in my future.

	Cool! Yeah, that was my concern too--one of the reasons I was
curious to know what happens when you guys go to 5.x.

> I absolutely agree but wanted to provide some information about what
> we've learned about Search.pm for folks who are thinking about it
> now.  Effort is better spent, in my opinion, on the refactoring to
> make it more easily understood and maintained than on having it emit
> better SQL, at least for those without large databases.

	Awesome, I'm glad we agree. I totally appreciate the data about
what you've learned, too--it's exactly this sort of information that
helps guide our future directions, even in refactoring! :-)

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.