On Mon, 2007-02-26 at 06:08 +0100, Michael Radziej wrote: > Hi, > > Malcolm Tredinnick wrote: > > In passing, moving the query construction out of QuerySet, particularly > > if we move the database access portions out as well, will make > > integrating with SQLAlchemy easier -- since it's "just another data > > storage backend". > > If you make it a design goal, yes. But I'd think that a generic > pluggable "data storage backend" together with your own backend is much > harder to get right than directly plugging in SQLAlchemy.
Let's stop going down this path. This isn't a thread about whether to switch to SQLAlchemy. If you want to work on that, there is a branch already created and a maintainer appointed for that branch. I've got nothing against it, but it's not an area I'm working on at the moment. Thanks, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
