-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The sqldiff command doesn't recognize GeoDjango and JSON fields #1010
Comments
Regretfully I did not have the time in the last year to properly continue to develop Probably recent versions of Django ORM also have better introspection tools for |
The part about JSONField is not fixed though. |
Any updates on JSONField support? |
Can we open a new issue for this ? Think for both |
Some database (postgresql) can store json in a |
exactly. The problem happens when some app uses the JSONField type of postgresql. |
The sqldiff is a great tool. However, I'm noticing that it does not recognize less common fields, such as PointFields from GeoDjango and JSON fields from the django-jsonfield project. Even if I run the alter statements that sqldiff suggests, sqldiff still reports difference in the output.
The sqldiff command doesn't seem to recognize geography columns from GeoDjango:
Code Sample:
Sqldiff output:
The sqldiff command doesn't seem to recognize geometry columns from GeoDjango:
Code Sample:
Sqldiff output:
The sqldiff command doesn't seem to recognize jsonfields (from django-jsonfield). I haven't tried with the newer built-in jsonfields yet, so maybe it will work with that?
Code Sample:
https://github.com/ImaginaryLandscape/django_site_config/blob/master/site_config/backends/model_backend/models.py#L110
Sqldiff output:
The text was updated successfully, but these errors were encountered: