-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2012 03:57 PM, Arnoud van Heuvelen wrote: [snip] > 2) Build a relation table that links the sessions to the users. (Or > use a CSV in the user object.) This could be done completely in the > auth package. Downside is that we have to create a new table. Upside > is again, that we could invalidate sessions on password change. [snip] > My favourite is option 2 for now. It seems the most resource friendly, > even though we need to save more data. I don't know what Django's > policy on adding tables is though.
This is not an option because the database session backend is only one of many session backends. Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8LD1IACgkQ8W4rlRKtE2eHmgCbBx/7FlOHfi32Cr1pNWa4mKsW Ca0An1rB+T9fwFwdlHzEmwj/PxTxIAd3 =Mj2V -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
