Index sort order, NULL behavior: NULLS FIRST / NULLS LAST

[janpio]

Seems our index sort order feature currently only lets your sort ascending or descending, but not define where the NULLs should be put: https://www.prisma.io/docs/concepts/components/prisma-schema/indexes#configuring-the-index-sort-order-with-sort

NULLS FIRST
Specifies that nulls sort before non-nulls. This is the default when DESC is specified.

NULLS LAST
Specifies that nulls sort after non-nulls. This is the default when DESC is not specified.

https://www.postgresql.org/docs/9.6/sql-createindex.html#:~:text=descending%20sort%20order.-,NULLS%20FIRST,-Specifies%20that%20nulls

CREATE INDEX "some_table_some_indexed_col_idx" ON "some_table"("some_indexed_col" DESC nulls last);

Variants of our sort orders that add NullsFirst and NullsLast to the available values seems like an easy way to fix this.

[DavidHancu]

👋 Hi @janpio!

I've been working on my NPM Package Prisma Util, which is all about implementing features that are requested by developers in the community. This issue has attracted my attention and I want to ask if anyone would be interested in this feature being added either to Prisma or Prisma Util.

Prisma Util already has enhanced migration parsing, so it should be able to handle this issue pretty easily.

[janpio]

Well, I work at Prisma so no need to build this for me. It is on our list of issues we are looking into.

[aseemk]

Hi @janpio & team. I just ran into the lack of this. Is this still planned for sometime? Alternately, this seems to be labeled "has-stopgap". Does that mean a workaround is available? What is that workaround if so? Thank you!

[janpio]

You should be able to generate a migration file, and then modify it before applying: https://www.prisma.io/docs/orm/prisma-migrate/workflows/unsupported-database-features#customize-a-migration-to-include-an-unsupported-feature