Expected behaviour for sort queries

[amaster507 (Anthony Master)]

Continuing the discussion from Identical query execution has inconsistent response:

@paulrostorp

it seems that it is dgraph’s behavior to filter out items that not posses the predicate you sorting on.

This does not seem like the right behaviour! No other database does this that I know of. I am familiar with SQL and MySQL so from that realm, if I sort based on nullish field in a column it will put the nullish order on top. This can be controlled with using CASE in the ORDER BY clause to move the nullish values to the end of the order though.

Possible to use SQL to sort by date but put null dates at the back of the results set?

Dgraph should have some kind of equivalent sorting of missing/nullish predicates. I understand that null predicates in Dgraph === missing predicates, which is not exactly the case in RDBs

Another Related Post:

Setting null value on predicate, and how has(predicate) and orderasc/desc or filter will effect results?

hi, i found in doc that if a field is set to null, its as like deleted the predicate from that object. for example updated_at = null if i were to sort a list of objects by updated_at, will it return records with updated_at set to null? if it does not return those records, means i have to set it to something that means empty right? if yes, what are the default values for null for all different data type of dgraph? int = 0? dateTime = ? string = “” ? float = 0.0 ? bool = false ? no null…