Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalA couple of reasons I prefer a single table:
(1) with multiple tables you'll almost always be performing unions and you pay for the core data multiple times
(2) you can easily optimize for a subset of attributes or a combination of devices and attributes with indexes and use sparse columns to minimize wasted space
I wrote a bit about EAV hereI wrote a bit about EAV here - it is by no means perfect, but we used it to solve many performance problems (at the cost of others) at mya previous job.
A couple of reasons I prefer a single table:
(1) with multiple tables you'll almost always be performing unions and you pay for the core data multiple times
(2) you can easily optimize for a subset of attributes or a combination of devices and attributes with indexes and use sparse columns to minimize wasted space
I wrote a bit about EAV here - it is by no means perfect but we used it to solve many performance problems (at the cost of others) at my previous job.
A couple of reasons I prefer a single table:
(1) with multiple tables you'll almost always be performing unions and you pay for the core data multiple times
(2) you can easily optimize for a subset of attributes or a combination of devices and attributes with indexes and use sparse columns to minimize wasted space
I wrote a bit about EAV here - it is by no means perfect, but we used it to solve many performance problems (at the cost of others) at a previous job.
A couple of reasons I prefer a single table:
(1) with multiple tables you'll almost always be performing unions and you pay for the core data multiple times
(2) you can easily optimize for a subset of attributes or a combination of devices and attributes with indexes and use sparse columns to minimize wasted space
I wrote a bit about EAV here - it is by no means perfect but we used it to solve many performance problems (at the cost of others) at my previous job.
