On Wed, Apr 23, 2014 at 5:43 PM, Shai Berger wrote:
> We are limiting the breaking of backwards compatibility as much as we can.
Fair enough.
> On the contrary, my
> intuition is that people using select_related are generally aware of the form
> of generated SQL, and should expect locking as the
On Thu, Mar 27, 2014 at 4:20 PM, Shai Berger wrote:
> The relevant tests do a select-for-update to verify that the "for update"
> clause is, indeed, added; and they happen to run in autocommit mode. They fail
> because, under Oracle, in autocommit mode, the automatic commit happens
> immediately a
On Sat, Apr 2, 2011 at 17:04, Marti Raudsepp wrote:
> The patch is quite simple and so far has worked with all queries
> generated by Django, for a few different applications. It added a
> noticeable speed boost
Oh, I forgot to mention, I'm using the patch together with
Hi list,
I wrote a proof of concept patch to add prepared statement support to
Django for the PostgreSQL backend. Note that it's just a hack to see
if this approach could work at all, I know it's badly written. :)
The patch is quite simple and so far has worked with all queries
generated by Djang
