Jay Parlar wrote: > On 8/30/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > 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. > > > > A question then: Once the SQLAlchemy stuff is in and solid, will there > be any reason *not* to use it?
The Django query syntax is a great way to map a flattened dict to a query. A flattened dict like, say, GET or POST data. ;) JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
