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
When queries are simple this approach is very nice to use, yes.
It gets complicated if you want to pass the object around or modify the where query.
We should also add the possibility to edit the where() statement, with a getter and setter for the object. Otherwise it is not possible to edit the where conditions. For example, you could have a base class with default where options that get modified by child classes.
It is not a use-case for me but I can imagine people want to build upon this behavior once it exists.
String parameters to where() with strings should be internally converted to an object in general? Isn't that what we do already?
Hey guys from what it seems I can't really use
I think it would be useful to avoid overwriting a lot of stuff and just basically passing a query to the current Model.
Kind Regards,
Luis Bizarro
The text was updated successfully, but these errors were encountered: