Hi all,
On Tuesday, June 19, 2012 5:12:47 PM UTC+3, Florian Apolloner wrote:
>
> Hi Greg,
>
> 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
Good to know about native migrations, and the interim solution seems
reasonable.
Thanks so much!
On Tuesday, June 19, 2012 10:56:38 AM UTC-5, Andrew Godwin wrote:
>
> On 19/06/12 16:13, Greg Aker wrote:
> > Florian:
> >
> > I don't think waiting for migrations in the Django core is totally
On 19/06/12 16:13, Greg Aker wrote:
> Florian:
>
> I don't think waiting for migrations in the Django core is totally
> necessary to fix a bug like this (or others that might be similar).
> With proper documentation in the release/upgrade notes, I think it's
> completely reasonable to expect
On 19/06/12 15:25, Stephan Jaensch wrote:
> 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
Florian:
I don't think waiting for migrations in the Django core is totally
necessary to fix a bug like this (or others that might be similar). With
proper documentation in the release/upgrade notes, I think it's completely
reasonable to expect someone working with Django to be able to run a
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
>
Hi Greg,
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
problems…).
Cheers,
Florian
--
You received this message because
I wanted to bring up this bug: https://code.djangoproject.com/ticket/17763
as it's bitten me on a couple of projects recently
Summarizing the ticket:
==
Django automatically generates a name that is longer than what the default
field length can hold.
INSERT INTO "auth_permission"
