Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the advantage in storing data as an object instead of storing them in separate table columns
For example:
storing an item details as Blob instead of storing the attributes separately in an items table (SKU, Name, Price etc)
In general, that sort of thing is discouraged. Blob columns are intended to store data that’s a large piece of binary information, like an image or the contents of a file. This is data that’s only stored and retrieved; it’s never queried against, indexed, or otherwise interacted with.
If you’re referring to storing data that would otherwise go into a column or table (a list of some kind, for example), then it’s not a good practice to employ. The database engine is designed to deal with these relationships and make storing, retrieving, querying, etc. against them simple and performant. Storing this data as a binary object means that you’re ditching the optimizations that the database gives you.
My general thoughts are this: there are many people that are smarter than I am who write these RDBMS systems; do I really think that I can outsmart them when it comes to storing a simple list?