Would be a great to get a confirmation on the deleted ndb.Expando properties being falsely set to None on the SDK I don't think there is anything to tamper with that process in my sdk/non-production-yet use case, however the idea that one of my routines is somehow falsely setting all of these attributes to None, or causing such a change is concerning.
So basically the issue is: When you delete a property(with no default value, but an explicitly set property at Model definition) from a ndb.Expando entity, should it be set to None? The answer should be no, however it's yes on the sdk On Tuesday, September 17, 2013 3:44:48 AM UTC+3, Kaan Soral wrote: > > class Test(ndb.Expando): >> a=ndb.StringProperty(repeated=True) >> b=ndb.StringProperty(repeated=True) >> c=ndb.BooleanProperty() >> d=ndb.StringProperty() >> >> t=Test( >> a=["1","2","3","4","5","6","7","8","9","10"], >> b=["1","2","3","4","5","6","7","8","9","10","11","12"], >> c=True, >> d="gg" >> ) >> delattr(t,"c") >> t.put() >> > > - kind: Test >> properties: >> - name: a >> - name: b >> - name: c >> - name: d >> direction: desc > > > For the above operation, SDK 1.8.2 calculates Write Ops as 172 - after > "c" gets deleted, the SDK sets it to None, and None is calculated in the > Write Ops, as a composite index member > I've tested the same thing on AppEngine itself, although I can't verify > 100%, the composite indexes is 0 bytes, so I'm assuming this is a SDK bug? > > Thanks in Advance > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
