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.
While rudimentary grouping and joining is possible with
BasicObject::selection
there are many cases where it just isn't possible to generate the needed SQL. For instance joining the table with itself needs table aliases which BO doesn't add. Grouping in general isn't BOs strong side but using aHAVING
condition is just not possible.This change allows for using a fully customized query (grouping, joining, etc) while still creating instances of your BO model similar to how
BasicObject::selection
does.It assumes the user know what he is doing (i.e. not selecting all the required fields it considered a programming error by the caller).