Hi,
I posted a bug almost a month ago, about set_language and i18n_patterns
failing in some cases when used together.
It didn't gather a single comment and is still in Unreviewed state, which
seems most unusual for this well kept bugtracker :)
https://code.djangoproject.com/ticket/26556
Do any
Le mardi 22 mars 2016 23:33:10 UTC+1, Shai Berger a écrit :
> It is Django's job to try, as best as it can, to fulfill these
expectations.
How could I disagree? Of course, if there is one single sensible, obvious
default, that would help 99.9 % of users, like your webserver analogy, it
should
Le mardi 22 mars 2016 00:11:31 UTC+1, Shai Berger a écrit :
> I disagree. The ORM cannot keep you safe against MySql's REPEATABLE READ.
>> Incidentally, to prove my point,
>> this has been changed in Django 1.9 and data-loss doesn't happen
anymore,
>> in that same default isolation level.
>>
Le lundi 21 mars 2016 13:35:19 UTC+1, Aymeric Augustin a écrit :
>
>
> The problem is to determine what “safe” means here :-) I’m afraid this
> won’t be possible in general (at least not in a remotely efficient fashion)
> because Django inevitably depends on the guarantees of the underlying
> da
