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
Containing related model in the query is a very different operation than setting view vars for select options for related models.
Also CrudView's ViewListener contains associated models in it's beforePaginate() and beforeFind(), so having a separate listener in Crud for containing would allow better control.
The text was updated successfully, but these errors were encountered:
Containing related model in the query is a very different operation than setting view vars for select options for related models.
Agreed.
Unfortunatley, the documentation could be more clear about this and the sad fact that the two behaviors can't be controlled separately, at the moment.
Also, the current behavior can lead the application to load the full data of potentially large database tables.
Because of this, we recently ran into a performance/memory limit issue.
Also CrudView's ViewListener contains associated models in it's beforePaginate() and beforeFind(), so having a separate listener in Crud for containing would allow better control.
While a separate listener would certainly be much cleaner, a simple flag for controlling the view variable population would probably be much easier to implement.
Also, less complicated to keep backwards compatibility.
If you are open to the idea of such a flag, me or my team mate @T0nyDamage would be interested to contribute.
Containing related model in the query is a very different operation than setting view vars for select options for related models.
Also CrudView's ViewListener contains associated models in it's beforePaginate() and beforeFind(), so having a separate listener in Crud for containing would allow better control.
The text was updated successfully, but these errors were encountered: