This very issue of a not-null constraint causes a problem with django-silk. I'm not sure this matters in practice, because the usage of django silk is usually for development; I just added an sqlite3 database alias and a router for django-silk. However, it validates the problem of the current approach.
-- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3fd3a890-6669-46d0-b79a-bf0dc86f2538%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
