38 reputation
7
bio website ninakin.com
location Los Angeles, CA
age 29
visits member for 1 year, 5 months
seen May 8 '13 at 0:01

I'm a web developer!


Mar
6
awarded  Supporter
Mar
6
awarded  Scholar
Mar
6
accepted Database Design - different objects with shared tagging
Mar
5
awarded  Autobiographer
Mar
5
comment Database Design - different objects with shared tagging
The tri-link table you mention was probably a result of me being mentally lazy... :P After reading the various answers, I'm thinking neither of my initial options make sense. Having separate separate ReportKeywords and RecommendationKeywords tables makes more practical sense. I was considering scalability, in terms of potentially having more objects that needed keywords applied, but realistically there's probably only one more object type that could need keywords.
Mar
5
comment Database Design - different objects with shared tagging
I'm using MS SQL Server for this project, but thanks for the info on PostgreSQL. The other points you brought up about deleting and making sure object-keyword pairs each occur only once. Even if I had keys for each object-keyword pair though, wouldn't I still have to check before inserting? As for having a separate keyword id... I read that for SQL Server, having a long-ish string could reduce performance, and I'm probably going to have to allow users to enter "key phrases" rather than just "key words".
Mar
5
awarded  Editor
Mar
5
revised Database Design - different objects with shared tagging
added 528 characters in body
Mar
5
comment Database Design - different objects with shared tagging
Good point! I'll have to spend some time thinking about this!
Mar
1
awarded  Analytical
Mar
1
awarded  Informed
Mar
1
awarded  Student
Mar
1
asked Database Design - different objects with shared tagging