Great work Jeff! PEP-8 for identity was on my own "black" list of things to fix. ;-)
I would suggest moving DeprecatedAttr to turbogears.util since this can be useful for other things also. Ciao Michele PS1: Next time move this type of announce and any discussion related to TG svn to the turbogears-trunk group ;-) PS2: Just curious, does SQLAlchemy need to use the horrific TG_User name also or it handles fqn names for tables? Jeff Watkins wrote: > As of r1107, I've moved SqlObjectIdentityProvider to pep8 style names > and I've also removed the visit.id (which was deprecated). In > addition, I've changed the alternate ID columns for TG_User, > TG_Group, TG_Permission from userId, groupId, and permissionId to > user_name, group_name, and permission_name. While the old attributes > will be supported, they generate a deprecation warning. However, the > database column names have changed to reflect the new names. I think > this makes things a little clearer -- removing the confusion between > userId (a string) and user_id (an int) in the join tables. > > Finally, I've also checked in my preliminary SqlAlchemy visit and > identity modules. THESE DON'T WORK. Some recent changes in the Trunk > of SQLAlchemy have made these simply not work, however I wanted to > get them checked in lest something horrific happen to my powerbook. > They were working this morning before I updated and now they don't work. > > -- > Jeff Watkins > http://newburyportion.com/ > > "Computers are like Old Testament gods; lots of rules and no mercy." > -- Joseph Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
