Recommended SQL database design for tags or tagging [closed]

by

Three tables (one for storing all items, one for all tags, and one for the relation between the two), properly indexed, with foreign keys set running on a proper database, should work well and scale properly. 

Table: Item
Columns: ItemID, Title, Content

Table: Tag
Columns: TagID, Title

Table: ItemTag
Columns: ItemID, TagID

More Related Contents:

  1. Database Design for Tagging [closed]
  2. Are soft deletes a good idea? [duplicate]
  3. What mysql database tables and relationships would support a Q&A survey with conditional questions? [closed]
  4. single fixed table with multiple columns vs flexible abstract tables
  5. DB design to use sub-type or not?
  6. What is the most efficient way to store tags in a database?
  7. Relational database design question – Surrogate-key or Natural-key?
  8. What are the principles behind, and benefits of, the “party model”?
  9. Best way to model Customer Address
  10. How to implement a many-to-many relationship in PostgreSQL?
  11. How to implement one-to-one, one-to-many and many-to-many relationships while designing tables?
  12. Create unique constraint with null columns
  13. What are best practices for multi-language database design? [closed]
  14. Database Structure for Tree Data Structure [closed]
  15. Database Design for Revisions?
  16. Storing money in a decimal column – what precision and scale? [closed]
  17. How to store a list in a column of a database table
  18. Serial numbers per group of rows for compound key
  19. PostgreSQL: Which Datatype should be used for Currency?
  20. Facebook database design?
  21. How to create a multi-tenant database with shared table structures?
  22. Name database design notation you prefer and why?
  23. Can I set ignore_dup_key on for a primary key?
  24. Select (retrieve) all records from multiple schemas using Postgres
  25. Which datatype should be used for currency?
  26. Use email address as primary key?
  27. Composite Primary Keys : Good or Bad?
  28. Which database design gives better performance?
  29. What does ON [PRIMARY] mean?
  30. can we have a foreign key which is not a primary key in any other table?

Leave a Comment