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 we order by ANY nullable field with DESC order, nulls are always on top.
That’s related to the default postgres ordering params, with NULLS FIRST set for DESC ordering.
Backwards compatibility, any ordering queries should still work with any changes.
Specifying the null order should be achieved by providing a new argument. eg orderBy: [ENTITY_FIELD_ASC, NULL_OPTION] if it doesn't break compatibility otherwise orderByNull: NULL_OPTION
The text was updated successfully, but these errors were encountered:
When we order by ANY nullable field with DESC order, nulls are always on top.
That’s related to the default postgres ordering params, with NULLS FIRST set for DESC ordering.
Postgraphile has an untested example of a plugin for this https://www.graphile.org/postgraphile/make-add-pg-table-order-by-plugin/#makeaddpgtableorderbyplugin
Requirements:
orderBy: [ENTITY_FIELD_ASC, NULL_OPTION]
if it doesn't break compatibility otherwiseorderByNull: NULL_OPTION
The text was updated successfully, but these errors were encountered: