The patch only removes the requirement to populate the fields, not the
fields themselves. They are still there to be used. Just optional.
Yes I know but the original poster refered to people having problems with it which makes sence, and since most people trying TG/identity for the first time wont dare to go into the TG code to dig up the TG_* classes.
It is much easier to just extend tg_users to add more fields or more
constraints than it is to remove the the requirement to populate
existing fields.
Yes your right, but it will be easier to just write whatever you want it to be, and it's more efficient (both in having all you need in one place and in performance)
In particular, the uniqueness constraint on the email
address doesn't make sense for a lot of apps. A person who is assigned
administrative privileges may very well also need a non-administrative
account for regular use, and yet have only one valid email address.
Yes your right about that but I think this discussion is beyond those 2 fields.
-Steve
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
