Visit tracking and identity are two separate features, i.e. you can use visit tracking without identity. Visit tracking depends on the first table and identity tracking (a separate Python module which is separate from but logically depends on visit tracking) uses the second.
Barry ----- Original Message ---- From: Eric Snow <[EMAIL PROTECTED]> To: TurboGears <[email protected]> Sent: Thursday, January 31, 2008 6:45:20 PM Subject: [TurboGears] why is the visits table separate from the visit_identity_table Here are the two tables in question: visits_table = Table('visit', metadata, Column('visit_key', String(40), primary_key=True), Column('created', DateTime, nullable=False, default=datetime.now), Column('expiry', DateTime) ) visit_identity_table = Table('visit_identity', metadata, Column('visit_key', String(40), primary_key=True), Column('user_id', Integer, ForeignKey('tg_user.user_id'), index=True) ) Why are these separated into two tables. It seems like that separation is artificial. Is it for performance reasons? If they are to be separate then why is there no foreign key in visit_identity_table pointing back to visits_table? Thanks. -eric ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
