Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Equal Code and Concept overloads are inconsistent with Tuple equality semantics #21

Open
rob-reynolds opened this issue May 29, 2019 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@rob-reynolds
Copy link

No description provided.

@brynrhodes
Copy link
Collaborator

Specifically, the Equal(Code, Code) operator description says Code equality is defined using tuple semantics, but then says that the operator returns null if either argument is null, or has any null components. As of CQL 1.3, tuple equality semantics only return null if the values have different components specified.

brynrhodes added a commit that referenced this issue Jun 10, 2019
@brynrhodes brynrhodes self-assigned this Jun 18, 2019
@brynrhodes brynrhodes added the bug Something isn't working label Jun 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants