Kevin schrieb: > I don't have identity.soprovider.model.visit set. I'll check that out.
Just found that this setting was introduced in TG 1.0.2 only. So you quickstarted the project probably with an earlier version. > I noticed the change from tg_visit_identity to visit_identity but did > expect it mattered due to: > > class VisitIdentity(SQLObject): > class sqlmeta: > table = "tg_visit_identity" Yes, but that's probably code from your model, and since you didn't have identity.soprovider.model.visit set, TG used the default VisitIdentity class, not the one in your model. And the default class now uses "visit_identity" as the table name, just as in a quickstarted model. The "tg_" prefix is now only used for the user and group tables. We cannot use "user" and "group" here, because they are key words in SQL so it would be a bad idea to use them as table names. I'll mention this issue in the upgrade instructions. -- Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
