We recommend doing so to ensure certain necessities are incorporated, such as MongoDB-specific migrations and having the settings.py file already modified for you so Django is using an ObjectId value.
Let me know if you have any other questions, I'd be happy to help.
I was tried to add the mongodb to a django site on production and was running into some issues when migrating the models, i thought of trying to do some performance metrics on queries comparing mongodb and postgress.
maybe in the official release we will have such an option, that would be great. i would prefer to integrate mongo on some ongoing projects rather than starting from scratch with the template.
Thanks for your question @chrisachinga!
We recommend doing so to ensure certain necessities are incorporated, such as MongoDB-specific migrations and having the
settings.pyfile already modified for you so Django is using an ObjectId value.Let me know if you have any other questions, I'd be happy to help.
Thanks for the response,
I was tried to add the mongodb to a django site on production and was running into some issues when migrating the models, i thought of trying to do some performance metrics on queries comparing mongodb and postgress.
maybe in the official release we will have such an option, that would be great. i would prefer to integrate mongo on some ongoing projects rather than starting from scratch with the template.
this is amazing to be honest @anaiyaraisin
Thanks for your reply @chrisachinga,
So we don't recommend using our library in production until our GA.
For any issues please open a GitHub issue or Jira ticket!
We appreciate your feedback so much. :)
Hi @chrisachinga, just a heads up, I have forwarded your feedback to my team and someone will be in touch to chat with you. :)
great, looking forward to the chat