Quantcast
Channel: What is the proper way to store 'metadata' in relational database? - Stack Overflow
Browsing all 6 articles
Browse latest View live

Answer by Sunil Anand for What is the proper way to store 'metadata' in...

You can create two new tables:1) Defining multiple asset attributes in the following table (as many as the asset may have)asset_idasset_attributeasset_value2) asset_attribute...

View Article



Answer by Burleigh Bear for What is the proper way to store 'metadata' in...

When I've been faced with this in the past, the "best" answer always ends up varying depending on how much processing I want to do in the database, vs how much in the client code. For what it's worth,...

View Article

Answer by Bill Karwin for What is the proper way to store 'metadata' in...

I'd recommend putting the common attributes like cost in conventional column. Then add one more column in which you put a serialized collection of all the other variable asset attributes.CREATE TABLE...

View Article

Answer by Nik Kashi for What is the proper way to store 'metadata' in...

You can add another table for asset_metadataasset_metadataasset_metadata_id,asset_id,metadata_name,metadata_valueif you want to normalize and categorize the metadata, normalize it to this...

View Article

Answer by Martin Petransky for What is the proper way to store 'metadata' in...

I would suggest this:assets ( id asset_type_id vendor_id cost purchase_date)asset_poperties ( id asset_id asset_property_type_id value)asset_property_types ( id property_type)asset_types ( id...

View Article


What is the proper way to store 'metadata' in relational database?

I have a table called assets, where an asset can belong to a user,team, or division, and possibly multiple of each. My issue is that the assets are highly variable, and can have properties associated...

View Article
Browsing all 6 articles
Browse latest View live




Latest Images