Hi there,
I'm looking for the right way to go about doing the following:
I'd like to have casual visitors to my site represented by a real
User object so that I can treat them uniformly in joins, and other
relations with the rest of the models' objects.
So I expect to have something like this:
class User(SQLObject):
display_name = StringCol(length=50,default="Guest")
status = StringCol(length=1,default='G') # G/Guest, U/User, ...
# other fields, email, password, etc
So I need to create a default guest object when a user first hits the
site and associate it with a visit.
When someone logs-in I need to find their real user object, associate
it with the visit, and delete their old guest object.
On logout I need to do the reverse, or something similar.
On signup I need to take their guest object, change its' status and
add in any new information - email, password, etc.
I've dug about in the visit and identity plugins? but I'm not sure if
I can be clever with the existing ones, or if I should replace the
default with my own identity derivative. I'm tending towards the
latter, but would appreciate any advice on the finer points of my
model - most derivatives just seem to deal with authentication variants.
Any suggestions?
Loving tg BTW.
Thanks,
Toby
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
