Re: Optimize Question

[Patrick Crowley]

I just tried that, but with mixed results.

Like before, when I added an index on publish, I get a 'range' join, but
it's still doing filesort.

> | theater | range | status_publish | 1 | NULL | 4279 | where used; Using
filesort

Any way around that?

Best,
Patrick

> An index on t (publish,photo,name_present,location_city) would be the
> most effiecient, I think.