Thanks for the advice -- your recommendations against this configuration
were a surprise to me...
It's making me rethink what I want (and how much I want it).
I'll post this as a comment to the first stackoverflow question so others
are made aware.
On Monday, September 9, 2013 10:17:10 PM
On Tuesday, September 10, 2013 6:47:41 AM UTC-4, Dennis wrote:
Thanks for the advice -- your recommendations against this configuration
were a surprise to me...
It's making me rethink what I want (and how much I want it).
I'll post this as a comment to the first stackoverflow question so
PS: from my google searching, the 2 references below (and their references)
are really the only mention of this approach on the web!
So, it would be great to get some definitive advice on this seemly
reasonable approach.
On Monday, September 9, 2013 6:04:23 PM UTC+8, Dennis wrote:
Any
Honestly, I wouldn't do this.
Django has a lot of magic under the hood, and it's ORM does some very
specific things to make this magic happen. It's not just the auth, it's
how everything is structured in the database and how the app integrates
with the database. You're likely to break things
The major problem is: everything in Django is mapped to the ORM. Even the
sessions. Sorry for being negative but that is my way to understand this.
2013/9/9 Jonathan Vanasco jonat...@findmeon.com
Honestly, I wouldn't do this.
Django has a lot of magic under the hood, and it's ORM does some
