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 SQLAlchemy but maintain compatibility with django auth -- a sweet combination! Of course, the django admin system would likely not work, but that's ok. I thought this combination would work without being too much of a headache. But when I posted this on the SQLAlchemy google group for advice, the response was negative: they do not recommend using this combination: https://groups.google.com/forum/#!topic/sqlalchemy/VlR2At_mUcE But the django experts are on the django mailing list, so I thought I would ask this group too. Just wondering if others have tried this combination and what issues might have come up. >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. 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 "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
