Native DISTINCT doesn't work when we used orderBy

          await fastify.prisma.user_info.findMany({
            distinct: ["role"],

            select: {
              role: true
            },
            orderBy: {
              role: {
                sort: "desc",
                nulls: "last"
              }
            }
          })

or use take and limit

          await fastify.prisma.user_info.findMany({
            distinct: ["role"],
            take: req.query.limit,
            skip: req.query.page * req.query.limit,
            select: {
              role: true
            }
          })

I created the issue: #22734

It looks like we have to work around this problem by using subqueries: https://stackoverflow.com/questions/9795660/postgresql-distinct-on-with-different-order-by

Has this feature request been dropped? Druue unassigned herself and there hasn't been made any progress for almost a year. Native distincts are really a pitfall in certain situations as performance penalty for in memory usage can be a few thousand percent.

A quick update, we plan to release this preview feature to GA between September 2025 - February 2026. Read more here: #26136

Been using this, and has decreased the load on our servers a lot! Can we create a optimisation for when distinct and select are the same? select distinct type ... is a lot more effienct than select distinct on (type) id, type