Skip to content

/ db

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

Jump to bottom

Clarify default query constraint compound behavior #499

Open
mcandre opened this issue Apr 22, 2019 · 1 comment
Open

Clarify default query constraint compound behavior #499

mcandre opened this issue Apr 22, 2019 · 1 comment

Comments

@mcandre
Copy link

@mcandre mcandre commented Apr 22, 2019

By default, sending multiple constraints to upper.io Find() behaves as a union (OR), which may surprise users expecting an intersection (AND). Can we make this default behavior more clear in the documentation and examples?
@Asday
Copy link

@Asday Asday commented Apr 22, 2019

I would argue against changing such a fundamental default, given that the library is presumably used in several thousand codebases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@mcandre @Asday
You can’t perform that action at this time.