Update of field called size

[blackvladimir]

When I do

cls.update('set_size' = 10)

I get

File "/usr/lib/python2.7/site-packages/mongoengine/document.py", line 327, in update
    return self.__class__.objects(**self._object_key).update_one(**kwargs)
File "/usr/lib/python2.7/site-packages/mongoengine/queryset.py", line 1563, in update_one
    update = QuerySet._transform_update(self._document, **update)
File "/usr/lib/python2.7/site-packages/mongoengine/queryset.py", line 1465, in _transform_update        
    field = cleaned_fields[-1]

It looks like the problem occurs when the field name is also match operator name (queryset.py:1416). I don't know your code so I don't dare to send patch but I think it can be solved by checking of length of parts variable.

[rozza]

Hi you need to use a double underscore:

cls.update('set__size' = 10)

[blackvladimir]

Oh sorry, it is typo in bug report. I am using double underscore and it does not work anyway.

[rozza]

Ah ok - what is cls? An object instance? Can you do provide a bigger test case as it should be well covered by the current test suite.

[m-vdb]

maybe the quotes ?

[blackvladimir]

Sorry for delay, I somehow forgot about it.
The problem is "size" is comparison operator but i used is as a field name. It is evaluated as comparison in transform.py:175 and then there is no field name.

It does not work for any Document or queryset update().

Is there any way how to escape the "size" so it will be parsed as field instead as comparison operator?

[rw]

Still a problem with mongoengine 0.8.7.

[m-vdb]

is it possible to use __raw__ in update ?

[inabhi9]

It's really needed to escape operators in queryset.

If it's not possible immediately, is it possible to add constrain to prevent same field name as operators?

[labroid]

Having now been bitten twice (can't use 'id' and can't update 'size'), can we at least have a list of things we can't use until this is fixed? Right now I find out what doesn't work when a new field name shows up and mongoengine crashes...

[nirgn975]

We really need this! A list of names we can't use will be a good temp fix.

[Yevgnen]

Still a problem with mongoengine 0.15.3.