Robin Munn wrote: > > The notes on implementation that Adrian posted pretty much match what > I'm thinking at this point. The plan is to make this 100% API > compatible (if possible -- you never know what will turn up once you > start implementing some idea), so that existing code doesn't need to > change. But if you want access to the underlying SQLAlchemy objects to > do something like a nine-table query involving five LEFT OUTER JOINs > and two subselects, well, you should be able to do that as well.
hi, this is great news... could you show some example code how would it work? like.... without sqlalchemy you would have to do this in raw sql, but with django+sqlalchemy, you could do that.... things like that? because i checked the sqlalchemy tutorial, and i see that it is a powerful framework... i just don't currently see how it would interact with django.... please don't take this wrong, i very much welcome this django/sqlalchemy integration... i'm just curious how exactly would it work... how will i be able to go "deeper" (from django-level into sqlalchemy level) when needed... or ...well..maybe it's too early to ask questions like this :) thanks, gabor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
