Thanks for the write-up. I use a similar method in the application I am writing. I created an InheritableSQLObject for Taggable then use that as the base for more specific objects. This way I can great a tag relationship between any number of tables. I use the (item, tag, user) tuple to track personalized tags and 'item' can come from any object derived from Taggable. If user is None than it becomes a globally available tag. I suppose I can generalize user to user_or_group and allow for more control when sharing tags...
Truthfully, the Keyword system for my CMS is identical to this - I have a MultipleJoin('Keyword') on my base Atom, and all descendants of Atom (Page, Folder, Blog, Entry, Comment, etc.) then have Keywords (or tags; call them what you will).
Matthew Bevan, Systems Administrator Top Floor Computer Systems Ltd. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
