The storage engine design doesn't support this; we just write the new data (or tombstone for delete). This is much more performant than having to check first if the row exists.
On Tue, Aug 26, 2014 at 5:51 PM, Sékine Coulibaly <scoulib...@gmail.com> wrote: > SQL allows for sqlca.sqlerrd[0] to yield valuable information > regarding how many rows were affected by a DELETE or an UPDATE > statement. This is useful to verify that a DELETE on a given primary > key really matched a row, or even better, get the exact count of > deleted rows. > > I just came through the following CQL document : > > https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=doc/native_protocol.spec;hb=refs/heads/cassandra-1.2 > . > > It looks like the CQL native protocol doesn't handle such error/return > codes. > > Any comment appreciated ! > > BR > > Sekine > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
