What is the most efficient way to store tags in a database?

by

One item is going to have many tags. And one tag will belong to many items. This implies to me that you’ll quite possibly need an intermediary table to overcome the many-to-many obstacle.

Something like:

Table: Items
Columns: Item_ID, Item_Title, Content

Table: Tags
Columns: Tag_ID, Tag_Title

Table: Items_Tags
Columns: Item_ID, Tag_ID

It might be that your web app is very very popular and need de-normalizing down the road, but it’s pointless muddying the waters too early.

More Related Contents:

  1. Recommended SQL database design for tags or tagging [closed]
  2. What’s the difference between identifying and non-identifying relationships?
  3. What are the design criteria for primary keys?
  4. Alternatives to Entity-Attribute-Value (EAV)?
  5. Should OLAP databases be denormalized for read performance? [closed]
  6. Should each and every table have a primary key?
  7. Database development mistakes made by application developers [closed]
  8. What’s wrong with foreign keys?
  9. Surrogate vs. natural/business keys [closed]
  10. What are database normal forms and can you give examples? [closed]
  11. What is the best design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  12. NoSql vs Relational database
  13. single fixed table with multiple columns vs flexible abstract tables
  14. Multiple schemas versus enormous tables [closed]
  15. First name, middle name, last name. Why not Full Name?
  16. Techniques for database inheritance?
  17. Supertype-subtype database design
  18. In terms of databases, is “Normalize for correctness, denormalize for performance” a right mantra?
  19. How should international geographical addresses be stored in a relational database?
  20. Which is a good design for a database table that can be owned by two different resources, and therefore needs two different foreign keys? [closed]
  21. What’s wrong with nullable columns in composite primary keys?
  22. Best representation of an ordered list in a database?
  23. Ideas on database design for capturing audit trails [closed]
  24. NULL permitted in Primary Key – why and in which DBMS?
  25. Versioning Database Persisted Objects, How would you? [closed]
  26. Best design for a changelog / auditing database table? [closed]
  27. What are some best practices and “rules of thumb” for creating database indexes?
  28. Need help in developing DB logic
  29. Databse architecture (single db vs client specific db) for Building Enterprise Web (RIA) application on cloud
  30. Database – Data Versioning [closed]

Leave a Comment