-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
fix: enable nulls first #893
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add a test for this in our compliance test suite (then it would be tested for all dbs) or at whatever place you may think is appropriate? Thanks :)
of course, I just forgot to put this PR as a draft PR |
🤖 I have created a release *beep* *boop* --- <details><summary>db-service: 1.15.0</summary> ## [1.15.0](db-service-v1.14.1...db-service-v1.15.0) (2024-11-14) ### Added * enable path expressions in infix filter after `exists` predicate ([#875](#875)) ([7e50359](7e50359)) ### Fixed * **`search`:** ignore invalid path expressions inside `@cds.search` ([#849](#849)) ([250edd5](250edd5)) * nested exists wrapped in xpr ([7e50359](7e50359)) </details> <details><summary>sqlite: 1.7.7</summary> ## [1.7.7](sqlite-v1.7.6...sqlite-v1.7.7) (2024-11-14) ### Fixed * boolean for sql_simple_queries ([#886](#886)) ([d8139fa](d8139fa)) </details> <details><summary>postgres: 1.10.4</summary> ## [1.10.4](postgres-v1.10.3...postgres-v1.10.4) (2024-11-14) ### Fixed * enable nulls first ([#893](#893)) ([6684436](6684436)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: Johannes Vogel <[email protected]>
OData demands
NULLS FIRST
forASC
andNULLS LAST
forDESC
. SQLite, HANA behave like that, for Postgres the default is the opposite which is now changed.