The name field in Permission model in django.contrib.auth module causes
problems when one of the fields' verbose_name length is larger than 39
characters because it's maximum length is 50.
(https://github.com/django/django/blob/master/django/contrib/auth/models.py#L63)
Django automatically prepe
Hi Burak,
This limitation has been known for a long time. It’s tracked here:
https://code.djangoproject.com/ticket/8162
Your second suggestion was implemented a few weeks ago:
https://code.djangoproject.com/ticket/18866
--
Aymeric.
On 16 nov. 2013, at 19:11, Burak Emre Kabakcı wrote:
> The
On Thursday, October 24, 2013 11:40:37 PM UTC+3, Anssi Kääriäinen wrote:
> Here is the full list of changes that potential for breaking user code:
> - If related object's default manager has default filtering, then
> .remove() and .clear() will not clear those items that are filtered out.
> -
Hi Aymeric,
Sorry for the duplication. It seems the patch is not merged for 1.6 release.
Burak Emre
On Saturday, November 16, 2013 8:52:18 PM UTC+2, Aymeric Augustin wrote:
>
> Hi Burak,
>
> This limitation has been known for a long time. It’s tracked here:
> https://code.djangoproject.com/ticke
On 16 nov. 2013, at 20:25, Burak Emre Kabakcı wrote:
> Sorry for the duplication. It seems the patch is not merged for 1.6 release.
Indeed, the 1.6 branch was forked from the development branch a few months ago,
before that change was committed.
--
Aymeric.
--
You received this message beca
On Nov 17, 2013, at 2:02 AM, Anssi Kääriäinen wrote:
> - Reverse ForeignKey .remove() will not use .save() - it will use .update()
> - so no model save signals, and overridden model.save() is missed, too.
+1 on the pre/post_update signals as they can be useful for a variety of
purposes.
Al
