Re: Very slow query when too many joins
James...
Each 'attribute' (field_id:value pair) needs a JOIN to look up (for a given ads_id).
(His original posting said "183" twice, that was probably a typo.)
The large number of JOINs is one of the evils of EAV schema design. (The index I suggested makes them faster.)
The slowdown at 26 joins is another evil. (The setting I suggested may help with that.)
The bottom line is that EAV does not scale and should be avoided. He needs 29 or so lookups. With JSON, only 1 is needed. Instead, the application splits apart the JSON and formats the output. But that is much faster.
Subject
Views
Written By
Posted
4718
June 05, 2016 09:17AM
1788
June 05, 2016 09:27AM
1580
June 05, 2016 10:14AM
1412
June 05, 2016 10:48AM
1409
June 05, 2016 10:56AM
1505
June 05, 2016 03:33PM
1228
June 05, 2016 03:41PM
1305
June 05, 2016 05:36PM
1239
June 06, 2016 02:23AM
1212
June 06, 2016 03:33AM
1064
June 06, 2016 08:36AM
1186
June 06, 2016 08:52AM
1263
June 06, 2016 09:02AM
1226
June 06, 2016 11:16AM
1321
June 06, 2016 08:29AM
1137
June 06, 2016 11:30AM
1208
June 06, 2016 12:08PM
1173
June 06, 2016 02:11PM
1200
June 07, 2016 03:40PM
1272
July 20, 2016 05:34AM
Re: Very slow query when too many joins
1234
July 20, 2016 09:37AM
1448
July 21, 2016 04:43AM
1121
July 22, 2016 10:59PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.