On Tue, Feb 10, 2009 at 12:36 PM, David Larlet <[email protected]> wrote:
> > > Le 10 févr. 09 à 17:53, Alex Gaynor a écrit : > > David, I think I mentioned this to you, but I believe that by using > > the new F() objects we can actually remove the raw SQL entirely, I'd > > need to put some more thought into this(and perhaps Malcolm already > > has) but it should be possible. > > Alex, I agree with you (not yet tried though), it's only a timing > issue. There are two possibilities: moving then reF()actoring or doing > both in the meantime/same patch. I adopted the first one because I got > no answer to my previous email and that's the blocking point to me, I > thought there were more chance that it get commited quickly keeping > the patch as simple as possible. > Now, if you think it's important to do both and provide some feedback > on the way I did the move I'll be glad to work on it. > > Regards, > David > > > > > From my perspective they don't need to be at once, but there's no point in moving a bunch of code if the new location won't make sense once we remove the raw SQL. I'll take a look at the patch this afternoon and give some thoughts. As for the F(), the question of whether that should be specific to SQL backeneds is interesting, I don't know enough about non-SQL backends to know if that type of query makes sense. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
