Django 2.2 and PostgreSQL 11

First thanks for this project!

It’d be great to see if the warnings/errors scheme on unsafe operation is something that could be integrated to Django’s core.

I just wanted to give you a small heads up that the DatabaseSchemaEditor schema editor will change a bit in Django 2.2 to allow for check and unique constraint additions through the Meta.constraints API. Most of the details are in https://github.com/django/django/pull/10406

Also PostgreSQL 11 allows non locking NOT NULL column addition so it’d be great to adjust the documentation in consequence and use pg_version detection to avoid raising an exception/warning when not necessary.

[charettes]

Thanks for all your hardwork, @tbicr!

[charettes]

Ahh you’re right about the weird way Django deals with database level defaults. This is already tracked in https://code.djangoproject.com/ticket/470 which you might want to CC.