Prisma

Are nested selects supported/planned? I can include the relation and filter it on the client, but a 'select as' would be nicer.

<@U01LMSEBM88> :wave:
Do you want to filter on the relations while fetching the parent’s data?

yes, but have the result as a separate field.

I would suggest creating a feature request <https://github.com/prisma/prisma/issues/new?assignees=&amp;labels=&amp;template=feature_request.md&amp;title=|here> then for the above.

<@U01LMSEBM88> I checked out the <https://github.com/prisma/prisma/issues/5617|request> you created, and a workaround could be something like this:
```await prisma.todo.findMany({
    include: {
      times: {
        where: { end: null },
        select: { start: true },
        orderBy: { start: 'desc' },
        take: 1,
      },
    },
  })```


I read the docs on pagination but was confused about the difference of this `offset` to `limit`. Does it need to go through all the results or is it O(1)?

You can use both with Prisma, the <https://www.prisma.io/docs/concepts/components/prisma-client/pagination#cursor-based-pagination|cursor based pagination> is more performant that offset based.

There's no cursor since it's not about pagination but just limiting the result to one row. But I guess the docs just mean that `skip` does not scale, not `take`.

Yeah. `take: 1` is just `limit 1` under the hood. So the above query should be fine for your use case.

ok, thanks. I'll leave the feature request open since there's no issue about subqueries.
The above is fine if I just want that field, but it does not allow include all `times` as well.

&gt; but it does not allow include all `times` as well.
I didn’t get this point.

It does not allow to get all rows and get the result of this query, whereas with a subquery you'd get the result as an extra field.