[
https://issues.apache.org/jira/browse/CASSANDRA-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Yaskevich updated CASSANDRA-2409:
---------------------------------------
Attachment: CASSANDRA-2409.patch
Format:
{noformat}
INSERT INTO
<CF>
(KEY, <column>, <column>, ...)
VALUES
(<key>, <value>, <value>, ...)
(USING
CONSISTENCY <level>)?;
{noformat}
Consistency level is set to ONE by default
> 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
>
> Attachments: CASSANDRA-2409.patch
>
>
> 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
