Re: how dod you get to do multiple mysql queries concurrently?
| From: | Richard Lynch | Date: | Tue, 05 Feb 2008 17:57:43 +0000 |
| Subject: | Re: how dod you get to do multiple mysql queries concurrently? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-268726@lists.php.net to get a copy of this message | ||
On Sun, February 3, 2008 6:08 pm, Jochem Maas wrote:
> of paginated data combined with user defined filters (e.g. a product
> list sorted by price, etc and filter on type/category/keyword/etc)
If you want GIS to be useful for that, you'd have to pretend that
something like "type" was, say, longitude, and "category" was latitude
and keyword was height, and then convert back and forth and...
If you can create ONE index in MySQL that contains ALL your WHERE and
ORDER BY fields, then you are golden.
MySQL can only use ONE index per query.
If your query uses WHERE clauses and/or ORDER BY clauses of fields
that are NOT in your index, then it will be "slow"
create index shopping_index on shopping(type, category, keyword, etc);
is probably going to be far more maintainable and provide a similar
performance boost.
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some indie artist.
http://cdbaby.com/from/lynch
Yeah, I get a buck. So?