>> 1) It's an easy fix.
>> 2) It's backwards compatible.
>> 3) It has no impact on performance.
>> 4) LOTS of people want it.
>>
>> and most importantly
>>
>> 5) We could stop asking for it.
>>
>> This issue is such an easy "sure, why not!?"
>>
>> Please, O benevolent dictators, listen to the p
Hi Florian,
Am 19.06.2012 um 16:12 schrieb Florian Apolloner:
> Django itself can't change that currently since there is no support for
> schema alteration in Core. Once we get that we can tackle issues like that
> and increase to a sensible limit. (both name and codename might cause
> problem
> I'd like to improve transactions handling in Django. The first step is the
> current emulation of autocommit with database-level autocommit.
>
[...]
> I don't see much point in providing an option to turn autocommit off,
> because starting a transaction is a much more explicit way to achie
Hi Roald,
Am 20.09.2011 um 15:52 schrieb Roald de Vries:
> Hi all,
>
> Is there a fundamental reason that I'm missing (other than "nobody's taken
> the trouble of writing it") that I can't do the following? If there isn't
> I'll create a ticket for it.
>
>class R(Model):
>user =
Hi everybody,
I'm the author of the patch for bug 8660. [0] The patch adds user permission
checking for admin inlines. Carljm has been very helpful at giving me pointers
and reviewing the patch. But since he's very busy at the moment, it would be
nice if someone else could try out the patch and
