Ross Lawley
Ross Lawley
Yeah, the aim was to stop all individual ReferenceFields racking up queries... But you removing all control over that is also bad.
I was thinking that it shouldnt be harmful to return `obj` hence the original path, but I can see your point. Have you got an example where it breaks things...
Not sure what to do here as it is native to MongoDB that save updates if exists and inserts if new. Just because you have a custom primary key, I'm...
I think thats a different issue to reported Mitar - is your issue with a custom pk when calling save() it does an update? On Thu, Dec 20, 2012 at...
Perhaps not using save would be a better idea! default should be a callable so: default=uuid.uuid4 might work. Ross On Thu, Dec 20, 2012 at 4:38 PM, Mitar [email protected] wrote:...
This should be fixed in 0.8 as we also check the MyDocument()._created flag as well to identify if we want to do a delta.
Fixed in flask-mongoengine by not using the TextField but a custom field type: `NoneStringField` that converts `u""` to None: See: https://github.com/MongoEngine/flask-mongoengine/blob/d103fdcb72b3e735609e13a39e8713d28419b154/flask_mongoengine/wtf/fields.py#L153-L163
Well I'd suggest using signals, but it all depends on how you update your documents. Doing a `save` in pymongo will overwrite a document and isn't atomic. We do some...
I dont think its a scary task - should be relatively trivial, its just we'd have to hook into every save (easy) and inject into every update call - maybe...
Having to bump to 0.8 as PY3 support came early!