Continuing the discussion from Using nulls first or nulls last in order by:
I finally gave it a try, but this does not work as expected.
TOrder.BuildSql attaches asc / desc at the end of my sql-projection...
.OrderBy(TProjections.Sql<Integer>('{' + EntDic.Entity.ValidFrom.PropName + '} NULLS LAST')) ?
generates:
ORDER BY A.VALID_FROM NULLS LAST Asc
wlandgraf
(Wagner Landgraf)
2
Indeed, it will always add either Asc
or Desc
after the projection.
but this prohibits using nulls last or anything like that.
we circumvent this using a coalesce sql projection, but this will ignore defined indexes...
so we would need some functionality to define how null values should be ordered...
wlandgraf
(Wagner Landgraf)
4
I suggest you file a feature request for that so we can eventually evaluate and implement it.
system
(system)
Closed
6
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.