Here's an accepted ticket to allow the use of prepare statements:
https://code.djangoproject.com/ticket/20516
On Wednesday, November 27, 2013 10:35:09 PM UTC-5, est wrote:
>
> Hi Russ,
>
> Since 1.6 has pooling support now, what do you think of prepared
> statements?
>
> I strongly suggest we ad
Hi Russ,
Since 1.6 has pooling support now, what do you think of prepared statements?
I strongly suggest we add them. It will make Django faster in large projects
Django may not want to be the whole stack but it's pretty much the fullest
stack in Python world now.
On Tuesday, 5 April 2011 23:4
On Sat, Apr 2, 2011 at 10:04 PM, Marti Raudsepp wrote:
> 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 qu
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 the
persistent connections
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
