-
Notifications
You must be signed in to change notification settings - Fork 1
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
Appropriate model field for location and json #3
Comments
I think those field only work for specific sql, such as postgresql or gis sql. I’m not sure but I think we can’t use both field at the same time.
|
https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#manually-selecting-a-database please refer to this! I think we can use multi-db but we should decide to use this system.. |
I read it. Well then, I think can use it! But I previously had a problem with gis model api and PointField, so please note that. 쓸수 있을것 같아요. 근데 제가 PointField넣었을때 makemigrations 과정에서 문제를 겪고 해결하지 못하고 필드를 바꾼 경험이 있어서 그 점 유의해주시고 코딩 하셔야 할것 같아요! |
OK! I will test in my branch and tell you the progress. Thanks! |
If you're planning to work on backend, I think you can use my branch... |
https://docs.djangoproject.com/en/2.2/ref/contrib/postgres/fields/#querying-jsonfield
https://docs.djangoproject.com/en/2.2/ref/contrib/gis/model-api/#pointfield
I think those fields are more appropriate because they're built-in field in django.contrib. How about using them???
The text was updated successfully, but these errors were encountered: