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
W dniu 24.10.2013 18:33, Gavin Wahl pisze:
I really like the idea of implementing this as a url pattern decorator.
This seems similar to Alex Gaynor's talk about everything being a view.
It's more flexible than a middleware because you can decorate any part
of the urls tree, such as the patterns
There was some discussion about call-through middlewares recently. The most
popular idea was to allow wrapping urls with decorators. This way it would
be possible to apply any decorator you want to only part of your views. If
you do it on root urls level, then you have something like INNER_DISPA
Hello all,
I've had some troubles with default callables in FKs and tracked it down to
one of my templates tags which returns a model class. I'm not sure if this
is considered kosher or not so feel free comment on that too.
In my template I have a something like:
{{ my_project_lookup_class.cl
