#3776: user sessions
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Contrib apps
Version: SVN | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------+-----------------------------------------
Comment (by anonymous):
Replying to [comment:1 Ben Slavin <[EMAIL PROTECTED]>]:
> I think that if you're looking to persist data, it belongs in a formal
model somewhere (perhaps !UserProfile, as you mention), not in sessions.
Well think this would be quite convenient. I mean I have like 5 types of
messages for my site users, and I want to put a "dont show this type of
message again", and this number keeps on changing as we keep on adding
minor features. Requiring a model update on each such change is wasteful
and error prone process. We are never going to do a query on any of these
parameters, and having columns after columns is just not clean. Imagine
documenting such 20 bool columns. And many times things change from bool
to enum, and sometime to more complicated data structures.
Not having user sessions just limits the number of things you would be
willing to store for users, and framework would end up dictating site
design.
--
Ticket URL: <http://code.djangoproject.com/ticket/3776#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
