making queryset.delete issue only a single SQL query

2010-09-10 Thread Tobias McNulty
Hi All, I may be missing something, but queryset.delete() seems oddly implemented in Django. It does a select to get all the IDs to be deleted, and then deletes them, in blocks of 100 I believe, by ID. Is there a reason it needs to do this and/or is it overly complex to implement as a single que

Re: A prompt 1.2.3 release

2010-09-10 Thread Eric Holscher
> There was a hudson server running IIRC, but > http://hudson.djangoproject.com/ is not responding to me. > > I took the hudson instance down because nobody was using it and it was costing me a decent amount of money to run per month. I still have the images around on Rackspace Cloud if the DSF or

Re: A prompt 1.2.3 release

2010-09-10 Thread Paul McMillan
> Which buildbot?  http://buildbot.djangoproject.com/waterfall doesn't > seem to be doing 1.2.X - from the logs for the ones marked 1.1.X: My mistake. It looks like it was partially converted to 1.2.x, but not completely - the tests run when changes are made to 1.2.x, but as you pointed out, it's

Re: Proposal: extending the storage backend api

2010-09-10 Thread Stephan Jäkel
Another update on this proposal: I just wrote a patch to make the described idea possible and recycled the already existing ticket http://code.djangoproject.com/ticket/10497 for that. You'll find a patch attached to the ticket. Stephan Jäkel wrote: Hi, this proposal is about extending the s

Re: parameterized apps (was: Re: Eric Florenzano's presentation slides)

2010-09-10 Thread Russell Keith-Magee
On Fri, Sep 10, 2010 at 6:37 AM, Javier Guerra Giraldez wrote: > On Thu, Sep 9, 2010 at 3:59 PM, Russell Keith-Magee > wrote: > >> What you're proposing here is two things: a LazyForeignKey, and >> configurable applications. > > not really, it's only configurable applications.  once you have that

Re: A prompt 1.2.3 release

2010-09-10 Thread Luke Plant
On Thu, 2010-09-09 at 18:47 -0700, Paul McMillan wrote: > > Unfortunately we didn't catch this failure in four weeks, the fact > > that the buildbot > > isn't running tests for the 1.2.X branch doeesn't help either. > > The buildbot actually is running the 1.2.x tests, it is just > unfortunately n

Re: #9459 forms.DateTimeField() looses microseconds

2010-09-10 Thread Thomas Guettler
Tobias McNulty wrote: > On Thu, Sep 9, 2010 at 5:43 AM, Thomas Guettler > wrote: > > Here is the patch: > > http://code.djangoproject.com/attachment/ticket/9459/datetime-microseconds-py25.patch > > If the python version is greater-equal than 2.6, it uses %f