There was an issue where Django decides to do an update instead of an insert which causes a malformed CQL query on the backend. I made a change to ColumnFamily model save method where it always passes force_insert=True. ColumnFamily is now required to utilize partition and clustering keys.
Coverage decreased (-0.9%) to 59.929% when pulling 8bd1b671872fb35f422cc0c1d950da2ddf9e5678 on sethdenner:fix-partition-key-insert into f5ec67cc6d8328d42189c369ddb86dd5af4d20ee on Knotis:master.
Coverage decreased (-1.3%) to 59.573% when pulling 162c850c0da1a37620510d710f0ff4c21a1fa617 on sethdenner:fix-partition-key-insert into f5ec67cc6d8328d42189c369ddb86dd5af4d20ee on Knotis:master.
Coverage decreased (-1.3%) to 59.573% when pulling 162c850c0da1a37620510d710f0ff4c21a1fa617 on sethdenner:fix-partition-key-insert into f5ec67cc6d8328d42189c369ddb86dd5af4d20ee on Knotis:master.
…sert
There was an issue where Django decides to do an update instead of an insert which causes a malformed CQL query on the backend. I made a change to ColumnFamily model save method where it always passes force_insert=True. ColumnFamily is now required to utilize partition and clustering keys.
Added some tests to cover this.