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
For the second part, I think we can add nulls extra operator that will change default behaviour. The problem (also related to default config) is: there is no way to know if the column/expression is nullable or not. This is mean that NULLS FIRST/NULLS LAST will be added into all ORDER BY clauses. It may be slow for databases without native NULLS FIRST/NULLS LAST support (MySQL and SQL Server). Unfortunately, I have no idea how to solve it.
The proposed syntax is shown below. Probably both fields should be required (to avoid ambiguity).
NULL
s order different in different databases. Sometimes we need to change it. There is no default/built-it support in Laravel nor Lighthouse.Useful links:
There are two parts:
@sortBy
nulls ordering (config) #111)@sortBy
nulls ordering (query) #119)For the second part, I think we can add
nulls
extra operator that will change default behaviour. The problem (also related to default config) is: there is no way to know if the column/expression is nullable or not. This is mean thatNULLS FIRST
/NULLS LAST
will be added into allORDER BY
clauses. It may be slow for databases without nativeNULLS FIRST
/NULLS LAST
support (MySQL and SQL Server). Unfortunately, I have no idea how to solve it.The proposed syntax is shown below. Probably both fields should be required (to avoid ambiguity).
Or better (it will affect only one clause):
Related to nuwave/lighthouse#2486, nuwave/lighthouse#2056
The text was updated successfully, but these errors were encountered: