[GH-ISSUE #446] crash via host oncest(s) #323

New issue

Open

opened 2026-02-26 10:30:50 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 10:30:50 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Dec 28, 2019).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/446

https://docs.djangoproject.com/en/2.0/releases/2.0/#foreign-key-constraints-are-now-enabled-on-sqlite

https://stackoverflow.com/questions/54163537/django-db-utils-integrityerror-foreign-key-constraint-failed-while-executing-li

is it that?

currently host is in BAD_HOSTS to not crash the process all the time.

Originally created by @ThomasWaldmann on GitHub (Dec 28, 2019). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/446 https://docs.djangoproject.com/en/2.0/releases/2.0/#foreign-key-constraints-are-now-enabled-on-sqlite https://stackoverflow.com/questions/54163537/django-db-utils-integrityerror-foreign-key-constraint-failed-while-executing-li is it that? currently host is in BAD_HOSTS to not crash the process all the time.

kerem commented

2026-02-26 10:30:51 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 28, 2019):

https://stackoverflow.com/questions/47620487/django-2-0-sqlite-integrityerror-foreign-key-constraint-failed

or that? Host.get_by_fqdn() maybe?

@ThomasWaldmann commented on GitHub (Dec 28, 2019): https://stackoverflow.com/questions/47620487/django-2-0-sqlite-integrityerror-foreign-key-constraint-failed or that? `Host.get_by_fqdn()` maybe?