Skip to content

Make it possible to write delete/update operations without using matching #410

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

Closed
sdeleuze opened this issue Jul 22, 2020 · 2 comments
Closed
Labels
type: enhancement A general enhancement

Comments

@sdeleuze
Copy link
Contributor

In Kotlin I can write:

  • op.delete<User>().from("users").matching(Query.empty()).all()
  • op.delete<User>().matching(Query.empty()).all()

But not:

  • op.delete<User>().from("users").all()
  • op.delete<User>().all()

Same issue for update options.

@mp911de mp911de added the type: enhancement A general enhancement label Jul 23, 2020
@mp911de
Copy link
Member

mp911de commented Jul 23, 2020

That's an oversight on our end that we should address.

@mp911de mp911de added this to the 1.1.3 (Neumann SR3) milestone Jul 23, 2020
mp911de added a commit that referenced this issue Jul 23, 2020
…ng matching.

Fluent operations now allow statement execution without the need to specify a Query object allowing for shorter statements.
mp911de added a commit that referenced this issue Jul 23, 2020
…ng matching.

Fluent operations now allow statement execution without the need to specify a Query object allowing for shorter statements.
@mp911de
Copy link
Member

mp911de commented Jul 23, 2020

That change is in place now.

@mp911de mp911de closed this as completed Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants