> +1 for the first syntax. The others are duplicating functionality
> that is already present via more aptly named methods. The first
> syntax is also more consistent with other ORMs.
Seconded.
Seems much more obvious, simple and explicit than the other options to me.
On Thursday, 28 Februar
Can we please change this so it defaults to off, and just document how to
turn it on and in what situations you should turn it on?
In my opinion this default-on feature caters to a very specific audience,
and will cause a lot of unexpected behavior with other users.
Here is the tl;dr of an argu
On 28 févr. 2013, at 20:09, David Cramer wrote:
> Can we please change this so it defaults to off, and just document how to
> turn it on and in what situations you should turn it on?
>
> In my opinion this default-on feature caters to a very specific audience, and
> will cause a lot of unexpe
One comment on the patch (which I generally approve of entirely):
It would be helpful to have a backend method that performers the "restore
connection between uses" function, rather than just use connection.abort() (of
course, the default implementation can use that). For example, on PostgreSQL
On Feb 28, 2013, at 11:09 AM, David Cramer wrote:
> Immediately for anyone who has configured more workers than they have
> Postgres connections (which I can only imagine is common among people who
> havent setup infrastructure like pgbouncer) things will start blowing up.
If they have this co
On 28 févr. 2013, at 22:05, Christophe Pettus wrote:
> It would be helpful to have a backend method that performers the "restore
> connection between uses" function, rather than just use connection.abort()
> (of course, the default implementation can use that). For example, on
> PostgreSQL, A
On Thu, Feb 28, 2013 at 4:10 PM, Christophe Pettus wrote:
>
> On Feb 28, 2013, at 11:09 AM, David Cramer wrote:
>
> > Immediately for anyone who has configured more workers than they have
> Postgres connections (which I can only imagine is common among people who
> havent setup infrastructure lik
It is most definitely not an "error" to have less connections available than
workers, considering workers may serve different types of requests, and will
now persist the database connection even after that request has finished.
It may not be "the most correct", but a concurrent connection is ve
On Feb 28, 2013, at 1:43 PM, David Cramer wrote:
> It is most definitely not an "error" to have less connections available than
> workers, considering workers may serve different types of requests, and will
> now persist the database connection even after that request has finished.
If you have
Hello, I made all tests green finally (all commits are tested under Python
2.7.3 and 3.2.3). The problem that took a few days to solve was that the
default engine should be recomputed after changing TEMPLATE_LOADERS setting
since its _template_source_loaders internal needs to be recalculated. I
On Thu, Feb 28, 2013 at 4:52 AM, Reinout van Rees wrote:
> On 27-02-13 21:21, Andre Terra wrote:
>
>> I wonder if these will ever be made available online for a fee, even if
>> months after the conference. For a hobbyist developer like me, coughing
>> up a few thousand dollars for the tickets, reg
11 matches
Mail list logo
