> There is no way to mimic IF NOT EXISTS on UPDATE and it's not a bug. INSERT and UPDATE are not totally orthogonal in CQL and you should use INSERT for actual insertion and UPDATE for updates (granted, the database will not reject our query if you break this rule but it's nonetheless the way it's intended to be used).
OK.. (and not trying to be difficult here). We can’t have it both ways. One of these use cases is a bug… You’re essentially saying “don’t do that, but yeah, you can do it.. “ Either UPDATE should support IF NOT EXISTS or UPDATE should not perform INSERTs. At least that’s the way I see it. Kevin -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
