cursor.callproc()

Hi all, For a very long time -- as far as I'm aware, forever -- we've had, in our cursor classes, a "callproc()" method that follows the callproc() definition of pep249[1]; this allows database stored procedures to be called. Recently, we've had a ticket[2] and PR[3] to enhance this method --

Multiple template engines for Django - week 2

Hello, Here's the second update: https://myks.org/en/multiple-template-engines-for-django/#2014-10-19 Best, -- Aymeric. On 12 oct. 2014, at 20:31, Aymeric Augustin wrote: > Hello, > > I just posted the first update on this project: >

Re: 1.8 release planning

On Saturday, October 18, 2014 1:17:58 AM UTC+2, Josh Smeaton wrote: > > I was thinking along the lines of a one page common upgrade issues that > summarised the back-compat changes from the previous releases, separated > under each release header. > We already have on page per release for

Re: Single SQL update to multiple values instead of multiple sequential queries

Hi Anshuman, On Sat, Oct 18, 2014 at 2:05 PM, Anshuman Aggarwal < anshuman.aggar...@gmail.com> wrote: > Please see this enhancement request: > https://code.djangoproject.com/ticket/23646 > > Unlike what Russ has suggested, I'm pretty sure that a single UPDATE query > with a large number (Ks/Ms)

Single SQL update to multiple values instead of multiple sequential queries

Please see this enhancement request: https://code.djangoproject.com/ticket/23646 Unlike what Russ has suggested, I'm pretty sure that a single UPDATE query with a large number (Ks/Ms) of updates will be significantly faster than doing multiple SQL UPDATE queries. If more people on the list feel