My only dissatisfaction is that other contributors to this list seem to do almost anything with very few lines of code, whereas I am using many. And, being a newbie I naturally worry that I am on the wrong pathway, having missed the turning. Thanks to both for your reassurance.
Mike On Oct 3, 11:59 am, Shawn Milochik <shawn.m...@gmail.com> wrote: > Your current approach makes sense. If you're concerned that you're > storing too much data in the session, you could just maintain a > session ID in the session and use that as a key for an sqlite3 > database or something, or even a model in your app's database, if that > makes sense. Is there any reason you're unsatisfied with the way > you're doing it? > > Shawn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
