Allowing UNSET_VALUE in cqlengine? [Feature request]

[Michał]

Currently there is no way to use UNSET_VALUE in the cqlengine ORM and setting None (null) triggers

implicit delete and therefore creation of unwanted tombstones. Are there any plans to support using UNSET_VALUE

in models?

[Adam Holmberg]

You are correct. Setting None is the same as explicitly deleting that field (the docs were recently expanded in these areas):

http://docs.datastax.com/en/developer/python-driver/3.8/api/cassandra/cqlengine/models/#cassandra.cqlengine.models.Model.create

http://docs.datastax.com/en/developer/python-driver/3.8/api/cassandra/cqlengine/models/#cassandra.cqlengine.models.Model.update

http://docs.datastax.com/en/developer/python-driver/3.8/cqlengine/faq/#how-can-i-delete-individual-values-from-a-row

The intent is to provide UNSET semantics by not setting a particular parameter in kwargs (as opposed to explicitly setting to None). Please be aware there is a read/update/write path that is not working perfectly in that regard. It is being addressed:
https://datastax-oss.atlassian.net/browse/PYTHON-719

Regards,

Adam Holmberg

--
You received this message because you are subscribed to the Google Groups "DataStax Python Driver for Apache Cassandra User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python-driver-user+unsub...@lists.datastax.com.