t;
> Where app is the django app name and listing is the model name. So that
> sounds to me like I'm seeing what everyone else is, the migration is just
> not applied on the database for some reason, but shows as being applied OK.
>
> // Chris
>
>
> On Wednesday,
es migration (0002_remove_content_type_name) is being
> marked as applied but not actually run in the database, that will help
> determine if this is a bug in Django or a problem elsewhere.
>
>
> On Wednesday, June 10, 2015 at 7:11:48 AM UTC-4, Devang Mundhra wrote:
>>
>> I am gettin
I am getting the same error on Django v1.8.2 after migrating from v1.7.7
The underlying error is this-
django.db.utils.IntegrityError: null value in column "name" violates not-
> null constraint
> DETAIL: Failing row contains (39, null, app_name, model_name).
>
>
On Friday, April 17, 2015 at
3 matches
Mail list logo
