We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
is_in
not_in
It will allow us to do this (using this example schema):
bands = await Band.objects().where( Band.id.is_in( Concert.select(Concert.band_1).where( Concert.starts_on > some_datetime ) ) )
Currently it would be two separate queries, which isn't a huge hassle, but less efficient:
band_ids = await Concert.select(Concert.band_1).where( Concert.starts_on > some_datetime ).output(as_list=True) bands = await Band.objects().where( Band.id.is_in(band_ids) )
Adding this should be pretty straight forward. Here are the Postgres docs.
It's a very common use case which I come across all of the time.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
It will allow us to do this (using this example schema):
Currently it would be two separate queries, which isn't a huge hassle, but less efficient:
Adding this should be pretty straight forward. Here are the Postgres docs.
It's a very common use case which I come across all of the time.
The text was updated successfully, but these errors were encountered: