Support DELETE
without providing full primary key
#421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Given a table with primary key ((partition1), column1, column2), Cassandra and the Node.js have a different behavior.
This PR changes the driver to conform to Cassandra's behavior.
Cassandra behavior
Allows
DELETE
statements which specify:DataStax Node.js driver behavior
Requires all of the primary key columns (i.e. partition key and clustering columns) to be specified.
Not providing all primary key columns will result in the following error:
Note on code review
This PR also changes the
ModelMapper
tests to have more indicative column names.To make the PR easier to review, this minor refactor was done in a separate commit.