Timeline for Eav model sql select only products with all 3 values?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2020 at 8:12 | comment | added | Lennart - Slava Ukraini | @user208176, the problem with EAV is that the complexity grows very fast when adding more attributes to the equation. N attributes will require N-1 joins and the table itself usually grows fast since everything is lumped into one table. If you want control over resource usage like CPU, disk etc, you should probably consider limiting the number of attributes that can be used by a query. | |
| May 4, 2020 at 7:00 | comment | added | user208176 | Thanks its exactly what i am looking for, is this good approach for ecommerce site filtering? i am doing tests with your given code for each request to show 20 results it takes 0.1 second, should i spend more cpu when scaling the application? | |
| May 4, 2020 at 6:57 | vote | accept | user208176 | ||
| May 4, 2020 at 3:52 | history | edited | danblack | CC BY-SA 4.0 |
added 9 characters in body
|
| May 4, 2020 at 1:46 | history | answered | danblack | CC BY-SA 4.0 |