Working off svn trunk, I see an inconsistency in the quickstarted identity model between the SQLObject and SQLAlchemy implementations. In SQLObject, the (built-in) integer primary key for identity tables is named "id"; in SQLAlchemy, the explicit primary key is prefixed with the name of the table: "user_id", "group_id", etc.
It doesn't appear that there's a problem using just "id" for PK columns in SA (I'm doing it for my non-identity tables). Is there any reason not to make the two implementations consistent? -- Tim Lesher <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
