I was wandering if it's a very bad idea to have one table that holds all the ids related to one entity?
For example let's say i have 3 tables each containing data about one user. Should i use an extra column called
settings table or should i use an extra table called
user_index and make use of
USER id email password salt created PROFILE id full_name bio SETTINGS id max_packets delivery_day USER_INDEX user_id profile_id settings_id
Will this make queries extra slow? Is it worth the extra code? Is it even a pattern? Maybe
EAV?(I mean i saw something similar in
Magento but i'm not sure if this is exactly the same). Can this provide any performance enhancement or just a 'OCD-feel-good' moment?
MySQL 5.7.26 and i was thinking about using
InnoDB as a storage engine. The app is going to be written in
PHP 7.3. OS Ubuntu