Open
Conversation
# Conflicts: # tortoise/queryset.py
seladb
commented
Mar 18, 2026
| assert result == expected | ||
|
|
||
|
|
||
| @requireCapability(dialect=NotEQ("mssql")) |
Contributor
Author
There was a problem hiding this comment.
MSSql limit syntax is different but it's not currently supported in _SetOperation which has its own implementation of _limit_sql() instead of using the dialect SQL. I guess we can leave it as a TODO for later
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add union query support in an API similar to Django's API
Addresses these issues:
#1507
#2056 (partially)
Description
Add union query support:
As opposed to Django, this API supports result of multiple models (in Django all results will be instances of the first model).
However, similar to Django, the requested field names and types should be the same across all queried models. This is because of how DBs support union queries.
Motivation and Context
It addresses the following issues:
#1507
#2056 (partially)
Also - it brings more feature parity with Django.
How Has This Been Tested?
Added test coverage for all written code. It was tested with MySQL, Postgres and SQLite.
Checklist: