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

#60: FIX: Make TableQueryBuilder's where(field) and and(field) have equivalent meaning #62

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

nvamelichev
Copy link
Collaborator

This way, where(field) does not replace the whole filter expression with itself, but gracefully adds query conditions instead, e.g.:

return db.computeInstances().query()
     .where("id.project").eq(project)
     .where("id.name").eq(name)
     .limit(10)
     .find();

…have equivalent meaning

...this way `where(field)` does not replace the whole filter expression with itself, but gracefully adds query conditions instead, e.g.:
```java
return db.computeInstances().query()
     .where("id.project").eq(project)
     .where("id.name").eq(name)
     .limit(10)
     .find();
```
@lavrukov lavrukov merged commit 3b42668 into main Apr 17, 2024
1 check passed
nvamelichev added a commit that referenced this pull request Apr 18, 2024
…have equivalent meaning (#62)

This way, `where(field)` does not replace the whole filter expression
with itself, but gracefully adds query conditions instead, e.g.:
```java
return db.computeInstances().query()
     .where("id.project").eq(project)
     .where("id.name").eq(name)
     .limit(10)
     .find();
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants