Guys The only thing I don't understand at the moment is: everyone understands that current implementation of ORM together with current implementation of sessions table doesn't allow to force insert and throw exception if it fails. So I can state this as a special case. Every framework has limitations and exceptions, here we get one of them. So why don't just redesign the sessions table and change the session implementation a bit to make it match current abilities of current ORM ? It's so simple and even more: it's already done! IP checking stuff touched just 3 lines of code, it requires just one minute to remove it. Or 4 minutes to make it optional. We already spent much more time discussing than it took to write and debug this code to me.
--~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
