Is EAV an appropriate design for a collection of coexisting metadata-rich "fact estimates" on...

Share this & earn $10
Published at : August 27, 2021

Is EAV an appropriate design for a collection of coexisting metadata-rich "fact estimates" on objects?

Helpful? Please support me on Patreon: https://www.patreon.com/roelvandepaar

With thanks & praise to God, and with thanks to the many people who have made this project possible! | Content (except music & images) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing | Music: https://www.bensound.com/licensing | Images: https://stocksnap.io/license & others | With thanks to user ypercubeTM (dba.stackexchange.com/users/993), user Michael Green (dba.stackexchange.com/users/36809), user btown (dba.stackexchange.com/users/60358), user Aaron Bertrand (dba.stackexchange.com/users/1186), and the Stack Exchange Network (dba.stackexchange.com/questions/93985). Trademarks are property of their respective owners. Disclaimer: All information is provided "AS IS" without warranty of any kind. You are responsible for your own actions. Please contact me if anything is amiss at Roel D.OT VandePaar A.T gmail.com Is EAV an appropriate design for a collection of coexisting metadata-rich "fact estimates" on...
database designeavmetadata