We didn't use Django-norel since it require to change django itself.
Instead we use mongoengine to replace the model, works good so far.
But use mongoengine you have to change those third party applications yourself.
-- On Sun, Oct 30, 2011 at 11:57 AM, Kurtis <kurtis.mullins@gmail.com> wrote:
Hey,
I started doing some heavier reading on MongoDB and realized that is
awesome! I took a look around at using it as a back-end for Django and
it seems like you have to use the Django-norel fork.
My question to those who have used it -- is it a fairly extensive
change to go from a standard relational backend to MongoDB? We already
have several models in place and are using quite a few third party
applications. I'd really love to make the switch with our current in-
development application if possible, but since we're on a deadline I
can't make any large changes at this point that will require a ton of
time.
The thing I love most about it is there doesn't appear to be any need
to do schema changes (since there is no DB Schema), which *seems* like
it would make life so much easier. I'm not sure if that's the case
when it comes to the real world.
I'm open to arguments for/against it as well.
Thanks!
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment