MySQL Forums
Forum List  »  Performance

Re: Very slow query when too many joins
Posted by: Rick James
Date: June 07, 2016 03:40PM

If all (or most) rows need the same 'attributes', then they should be columns. If you have different attributes for different rows, then JSON is better. Example: A shopping site with cameras, dresses, tools, etc, all in the same table.

More on the evils of EAV: http://mysql.rjweb.org/doc.php/eav .

Joomla can get away with whatever it says because it does not plan on implementers having more than a few hundred items in their tables.

Options: ReplyQuote


Subject
Views
Written By
Posted
4354
June 05, 2016 09:17AM
1629
June 05, 2016 09:27AM
1247
June 05, 2016 10:48AM
1248
June 05, 2016 03:33PM
1127
June 06, 2016 02:23AM
1096
June 06, 2016 03:33AM
1101
June 06, 2016 09:02AM
1052
June 06, 2016 11:30AM
1052
June 06, 2016 02:11PM
Re: Very slow query when too many joins
1087
June 07, 2016 03:40PM


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.