On 8/30/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > What impact will this change have on existing queries? > > If the intention is to make the Django->SQLAlchemy model transition as easy > as replacing an import statement, what is the transition plan for existing > queries? > > Will the model.objects.filter(...) syntax continue to work for SQLAlchemy > models? > > Is the intention to phase out the existing query syntax in preference for > SQLAlchemy query syntax? Or will Django query syntax be maintained as a > 'query Lite' syntax for simple problems?
The goal is that this will have *zero* effect on existing queries. The Django query syntax will remain exactly the same, and the database API will stay the same. The only difference is that the SQLAlchemy backend will have *extra* functionality -- namely, that people will be able to fall into SQLAlchemy syntax if they want to. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
