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
I'm wondering what are your thoughts - and if you would be open for a potential PR - on having an option to filter fields by Having instead of Where.
The main use case in my scenario is that I'm trying to paginate through a table that has an aggregated value (e.g. sum(total)) and trying to paginate on top of that.
Thanks!
The text was updated successfully, but these errors were encountered:
Sure, we are welcome to pull request for any good idea. This is truly a scenario that this library not yet supported.
There might be challenges to integrate having aggregation patterns and also keep compatible with the original where model. To be honest I don't have much ideas on how to implement it at this moment. I would appreciate any attempt to bring this feature into reality 💪
Hello 👋
I'm wondering what are your thoughts - and if you would be open for a potential PR - on having an option to filter fields by
Having
instead ofWhere
.The main use case in my scenario is that I'm trying to paginate through a table that has an aggregated value (e.g.
sum(total)
) and trying to paginate on top of that.Thanks!
The text was updated successfully, but these errors were encountered: