I'm integrating MongoDB using MongoEngine. It provides auth and session support that a standard pymongo setup would lack. In regular django auth, it's considered bad practice to extend the User model since there's no guarantee it will be used correctly everywhere. Is this the case with mongoengine.django.auth? If it is considered bad...
Hi folks, my "table" look like this: {'name':'Rupert', 'type':'Unicorn', 'actions':[ {'time':0, 'position':[0,0], 'action':'run'}, {'time':50, 'position':[50,0], 'action':'stoprun'}, {'time':50, 'position':[50,0], 'action':'jump'}, {'time':55, 'position':[50,0], 'action':'laugh'}, ... ]} any way I can index the it...
I've been diving into MongoDB with kind help of MongoKit and MongoEngine, but then I started thinking whether the data mappers are necessary here. Both mappers I mentioned enable one to do simple things without any effort. But is any effort required to do simple CRUD? It appears to me that in case of NoSQL the mappers just substitute one...
I am quite new to both django and mongoengine. Is there any project I can refer to see basic implementation of user authentication and authorization. ...
Have you used MongoEngine or MongoKit with Django? Which one do you prefer? Background: I'm developing a new site and have experience with normal Django development but for the kind of data I'll be using the MongoDB will be better suited than a SQL database. I'm using Python 2.7 and can compile/install anything on my host so that's no...
I'm building a Django application that uses MongoDB and MongoEngine to store data. To present a simplified and version of my problem, say I want to have two classes: User and Page. Each page should associate itself with a user and each user a page. from mongoengine import * class Page(Document): pass class User(Document): name...