We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Open SGID sorts NULL values in the opposite direction than the SGID and esri file geodatabases.
NULL
A PostgreSQL order by ascending query will order NULL values last, while the SGID (Microsoft SQL Server) and file geodatabases order them first.
Invert the sort to have NULL values ordered they way you would like.
The PostgreSQL language supports the NULL value ordering in the ORDER BY clause. documentation
ORDER BY
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;
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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 theORDER BY
clause. documentationThe following will crash ArcGIS Pro version < 2.5 if used as a query layer query.
The text was updated successfully, but these errors were encountered: