[wp-trac] [WordPress Trac] #26281: Optimizing meta_query generated SQL? -> 9s to 20ms
WordPress Trac
noreply at wordpress.org
Sun Jan 19 15:25:37 UTC 2014
- Previous message: [wp-trac] [WordPress Trac] #26281: Optimizing meta_query generated SQL? -> 9s to 20ms
- Next message: [wp-trac] [WordPress Trac] Batch modify: #11235, #11697, #12721, #12955, #13412, #13926, #15946, #15963, #17374, #17455, #18266, #18362, #18701, #21234, #21641, #23168, #23169, #24672, #25267, #25397, #25838, #26284, #7745
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
#26281: Optimizing meta_query generated SQL? -> 9s to 20ms
-------------------------+------------------------
Reporter: vprat | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Query | Version: 3.8
Severity: major | Resolution: duplicate
Keywords: has-patch |
-------------------------+------------------------
Changes (by nacin):
* status: new => closed
* resolution: => duplicate
* milestone: Awaiting Review =>
Comment:
Replying to [comment:3 vprat]:
> Apparently, the optimisation would not be valid for AND relation.
However, this is perfectly right for OR relation.
>
> So I guess just writing a special case for the OR relationship (in which
case just use a single JOIN) would do the trick.
Indeed, on all counts! Feel free to jump in on #24093 if you can help.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/26281#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
- Previous message: [wp-trac] [WordPress Trac] #26281: Optimizing meta_query generated SQL? -> 9s to 20ms
- Next message: [wp-trac] [WordPress Trac] Batch modify: #11235, #11697, #12721, #12955, #13412, #13926, #15946, #15963, #17374, #17455, #18266, #18362, #18701, #21234, #21641, #23168, #23169, #24672, #25267, #25397, #25838, #26284, #7745
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the wp-trac
mailing list