You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be mitigated with .fields(for: PrimaryModel.self) or individual .field() invocations
The default behavior of returning all joined columns can not be changed without breaking compatibility due to the availability of the .all(Model.self, \.$keypath) overload (which would suddenly stop working at runtime without warning).
This is something we should definitely consider handling differently for Fluent 5, as it's a significant performance consideration.
Since we can't safely change the behavior for existing code, this is a wontfix for Fluent 4.
Describe the bug
When running a Fluent query with the following
join
:The generated query is:
This results in a potentially large extraneous amount of data being sent over the wire.
To Reproduce
Run a query with a join + filter
Expected behavior
The query should not return the column set for the joined table unless it's asked for via
.field
or.with
.Environment
Additional context
N/A
The text was updated successfully, but these errors were encountered: