OK - that example was from the page I was researching
Mine would be
all three columns in `bookmark` are together a unique key
(itemVersion is for display data, it doesn't actually represent another item)
So from what you are saying...
- if the tag names are small enough, you could replace tag_id in tagmap with name (wouldn't this render the tag column useless?)
- get rid of id in tagmap, and make bookmarkID/name the primary key in it
I trust your call, but am trying to get my head around how future changes would be more of a hassle with the "scuttle" solution?
For example, to add in a new tag at a later date, wouldn't I need to update MORE tables?
I'm a little confused, as, unless I'm misunderstand, Felgall's suggestion seem to revert the system back to a "scuttle" one, which is against what Old Pedant suggests.
Last edited by shaunthomson; 02-11-2013 at 03:18 AM..