-
Notifications
You must be signed in to change notification settings - Fork 0
PostgreSQL NULL sorting behavior #6
Copy link
Copy link
Open
Labels
known-issueWe understand there is an issueWe understand there is an issuewith-workaroundThis issue has a work aroundThis issue has a work around
Description
The problem
The Open SGID sorts NULL values in the opposite direction than the SGID and esri file geodatabases.
The reason
A PostgreSQL order by ascending query will order NULL values last, while the SGID (Microsoft SQL Server) and file geodatabases order them first.
The workaround
Invert the sort to have NULL values ordered they way you would like.
Examples
The PostgreSQL language supports the NULL value ordering in the ORDER BY clause. documentation
The following will crash ArcGIS Pro version < 2.5 if used as a query layer query.
SELECT * FROM municipal_boundaries ORDER BY minname NULLS FIRST;Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
known-issueWe understand there is an issueWe understand there is an issuewith-workaroundThis issue has a work aroundThis issue has a work around
Type
Fields
Give feedbackNo fields configured for issues without a type.