[jira] [Commented] (CASSANDRA-2409) Add INSERT support to CQL

["Eric Evans (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014136#comment-13014136 ] 

Eric Evans commented on CASSANDRA-2409:
---------------------------------------

I don't think this is a good idea. {{UPDATE}} already has semantics that are going to be a surprise to folks coming from SQL. Implementing {{INSERT}} to have identical semantics is going to be (IMO) more surprising still, not less.

But, I don't want to get wrapped up in a protracted debate about it, so I'll leave this as "-0", and let you guys carry-on as you see fit.

P.S. Please don't wait too long, the freeze is looming.

> Add INSERT support to CQL
> -------------------------
>
>                 Key: CASSANDRA-2409
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2409
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>             Fix For: 0.8
>
>
> There are two reasons to support INSERT:
> - It helps new users feel comfortable (everyone's first statement will be to try to INSERT something, we should make that a positive experience instead of slapping them)
> - Even though it is synonymous with update it is still useful in your code to have both to help communicate intent, similar to choosing good variable names
> The only downside is explaining how INSERT isn't a "true" insert because it doesn't error out if the row already exists -- but we already have to explain that same concept for UPDATE; the cognitive load is extremely minor.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira