New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sources for Django/SQLAlchemy statement #48

Open
piroux opened this Issue Feb 27, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@piroux

piroux commented Feb 27, 2015

In the Django article, section Django ORM resources, lines 223-227, about the future integration of SQLAlchemy in Django :

Note though that some of the Django core committers believe it is only a matter of
time before the default ORM is replaced with SQLAlchemy. It will be a large
effort to get that working though so it's likely to come in Django 1.9 or
later.

It is the first time I hear about this. But what a delight !
However the only public thing close to it, that I found, was a 6-year old branch in the django repo. So it cannot be what you are talking about because you initially made this statement in June 2014 (03bb450).

Could you add a bit more context to this statement :

  • How did you reach this conclusion ? Who/What are your sources ?
  • Who are these adventurous core committers ?
  • Have they already started a branch for this endeavor ?

Still, thank you for your well-organized educational website !

@mattmakai

This comment has been minimized.

Show comment
Hide comment
@mattmakai

mattmakai Feb 27, 2015

Owner

Yea it's been awhile since I updated that line, I expected there would be more activity around this in late 2014 / early 2015. The statement was based on random conversations I had with some of the core committers at DjangoCon US in 2013. The conversation was essentially that the templating system and the ORM should be more easily interchangeable if a developer wants to use Jinja2 on the front end or SQLAlchemy on the back end.

Multiple template engines are happening in 1.8 but I haven't heard anything on the ORM front lately. Looks like I'll have to do some more research if 1.9 is doing anything about multiple ORMs. If not, I'll go in and update the Django page to make it clear this isn't happening in the near term.

Does that help? I didn't mean to mislead or create false hopes.

Owner

mattmakai commented Feb 27, 2015

Yea it's been awhile since I updated that line, I expected there would be more activity around this in late 2014 / early 2015. The statement was based on random conversations I had with some of the core committers at DjangoCon US in 2013. The conversation was essentially that the templating system and the ORM should be more easily interchangeable if a developer wants to use Jinja2 on the front end or SQLAlchemy on the back end.

Multiple template engines are happening in 1.8 but I haven't heard anything on the ORM front lately. Looks like I'll have to do some more research if 1.9 is doing anything about multiple ORMs. If not, I'll go in and update the Django page to make it clear this isn't happening in the near term.

Does that help? I didn't mean to mislead or create false hopes.

@piroux

This comment has been minimized.

Show comment
Hide comment
@piroux

piroux Mar 18, 2015

I just found out that there is such a proposal in the Django GSoC 2015 Ideas :
https://code.djangoproject.com/wiki/SummerOfCode2015#SQLAlchemyNoSQLintegration

But it would be only a PoC :

The code produced under part (1) would be a standalone repository and project, not a candidate for inclusion into Django itself. Django won't be gaining official SQLAlchemy support - but we will be able to point at a viable proof of concept.

piroux commented Mar 18, 2015

I just found out that there is such a proposal in the Django GSoC 2015 Ideas :
https://code.djangoproject.com/wiki/SummerOfCode2015#SQLAlchemyNoSQLintegration

But it would be only a PoC :

The code produced under part (1) would be a standalone repository and project, not a candidate for inclusion into Django itself. Django won't be gaining official SQLAlchemy support - but we will be able to point at a viable proof of concept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment