Problem updating resource containing EmbeddedListField of Resource containing ReferenceField (and other fields) about django-tastypie-mongoengine

[mitar]

Please create a pull request with failing test.

[m-vdb]

yep, trying to find where it bugs with my best friend pdb, and if i succeed you'll have a pull request with a fix :D

[mitar]

No no. You can also just make a pull request with a test which fails. And then I can also look.

[m-vdb]

ok as you want, but since I need this to be fixed asap, I'll investigate too

[mitar]

OK. So yes. You can create pull request with test. And then later on augment it with another commit with a fix. :-)

[m-vdb]

done :)

btw, is there any support for DateTimeField ? (I can't see any document with a mongoengine.DateTimeField in documents.py)

[mitar]

Yes, that one should be automatically available in resource.

[m-vdb]

okay, I have something that fails, so I'll do another pull request.

For the first problem, I identified the cause :

in File tastypie_mongoengine.resources.py, line 475:

def obj_get(self, request=None, **kwargs):
    # MongoEngine exceptions are separate from Django exceptions, we combine them here
    try:
        return super(MongoEngineResource, self).obj_get(request, **kwargs)

In the returned function, tastypie does a query on the documents, and uses filter(**kwargs) on the queryset. And kwargs contains resource_uri, so that fails. A quick fix for me would be inserting kwargs.pop('resource_uri', None), but maybe this can be inserted upstream.

[mitar]

You are doing invalid REST request.

[m-vdb]

hum why is that ? could you explain a little more ?

[mitar]

See the test I fixed.

[m-vdb]

ok thanks for your help. Btw, my request was not that invalid. If I remove 'put' from the ExporterResource.allowed_method, the problem does not occur and everything goes well. Anyway, thanks for your help and your plugin 👍

[mitar]

That's semi-normal. :-)

To be user friendly, you can specify referenced document by any unique combination of fields (like id). But on the other hand you can also in-place create a referenced document by specifying values. And then there is another user friendly thing: if there is some additional field in the request which is not in the document, it is ignored. Sometimes it can be not so intuitive how this interacts. :-) resource_uri is not a real field so when it tries to do a query it fails with error above. If you would remove resource_uri but leave other two fields, it should work. On the other hand, if it tries to create a new referenced document, it ignores resource_uri and just creates a new embedded document. So I am not so sure "problem does not occur" really happens. Probably it creates another referenced document, it does not reference the one you want.

This happens when you want to be user friendly and resolve ambiguities. :-)

[m-vdb]

wow thanks for the explanation. I'll check that it does not create another document and that it does exactly what I want :-)

[mitar]

OK, maybe that auto-creation does not really work always. :-)