New version is giving this error 'null value in column "deleted_by_cascade" violates not-null constraint'

[jatindergit]

null value in column "deleted_by_cascade" violates not-null constraint

[Gagaro]

Thanks for the report, could you show me the migration generated to add this column? It should be set to False by default.

[jatindergit]

sorry, just downgrade the version but looks like its set to None instead of False

…

On Wed, Jun 8, 2022 at 3:11 PM Gagaro ***@***.***> wrote: Thanks for the report, could you show me the migration generated to add this column? It should be set to False by default. — Reply to this email directly, view it on GitHub <#208 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADSZDP2P6MCBCO4FYUGGDRLVOBTDTANCNFSM5XD37EQA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- *Jatinder Singh (Senior Software Eng.)* Mobile: +91 7696312994 Email: ***@***.***

[anuj9196]

@Gagaro Here is the migration file generated in my project

    operations = [
        migrations.AddField(
            model_name='question',
            name='deleted_by_cascade',
            field=models.BooleanField(default=False, editable=False),
        ),
    ]

[Gagaro]

Thanks for the migration file.

That's strange, you do have default=False. Could you give me the output of manage.py sqlmigrate of your migration?

[msteffeck]

That's strange, you do have default=False. Could you give me the output of manage.py sqlmigrate of your migration?

You never got a response, but my team just ran into this also.

BEGIN;
--
-- Add field deleted to xxxxxxxxxxx
--
ALTER TABLE "xxxxxxxxxxx" ADD COLUMN "deleted" timestamp with time zone NULL;
--
-- Add field deleted_by_cascade to xxxxxxxxxxx
--
ALTER TABLE "xxxxxxxxxxx" ADD COLUMN "deleted_by_cascade" boolean DEFAULT false NOT NULL;
ALTER TABLE "xxxxxxxxxxx" ALTER COLUMN "deleted_by_cascade" DROP DEFAULT;
CREATE INDEX "xxxxxxxxxxx" ON "xxxxxxxxxxx" ("deleted");
COMMIT;

It appears Django removes the default values from the table after the initial column creation. This is "normal" behavior.
https://stackoverflow.com/questions/42370160/django-postgresql-dropping-column-defaults-at-migrate

I suspect the code in the library (or in our code) is explicitly setting the value to None, so the Django field default is not applied. I will investigate further.

UPDATE:
There is nothing wrong with your code. It was an issue on our end.