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 advice (or potential problems) with using sqlalchemy with the django > framework but keeping the django user auth module? > > The django ORM would be used for the auth module (and its user table). > SqlAlchemy ORM would be used for other tables and also to read (but not > write) the django user table. > > This combination would allow the power of sqlachemy but maintain > compatibility with django auth -- a sweet combination! > Of course, the django admin system would likely not work, but that's ok. > > Just wondering if others have tried this and what issues might have come > up. > > This approach is described in the stackoverflow comment here: > > http://stackoverflow.com/questions/18465197/how-do-i-start-with-django-orm-to-easily-switch-to-sqlalchemy#comment27166795_18476898 > > The method to integrate sqlalchemy into django is described here: > > http://stackoverflow.com/questions/6606725/best-way-to-integrate-sqlalchemy-into-a-django-project > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
