Jan Piotrowski
Jan Piotrowski
Does the same happen without the `take: 10`?
I didn't want to suggest that this is the solution, just get context. The `ORDER BY` makes sure that you always get the same 10 results. Otherwise, this would not...
Right now you can't, this is not an option in Prisma as we need to guarantee the order as soon as `take` or `skip` come into play - otherwise running...
I don't know if there is such a spec test. The above is based on conversations with some engineers, and a experimental PR here that shows that this (with the...
It will not, as it makes some tests fail and changes how Prisma behaves. The PR was just to test how it behaves exactly.
Internal note: Confirm ordering behavior with and without `take` in query via SQL query logging. Also, does this really make the query slower when correct indexes are in place?
Good observation @askkaz. Can you maybe create a separate issue for the case of the `count()` query where an order is not even surfaced in the returned data? Thank you.
> A related nice-to-have feature would be to filter out generation of certain models during DB introspection. I have introspected a DB whose schema I don't own. I'll be accessing...
Can you provide a bit more extensive explanation problem what problem happens when exactly @rivatove? Optimally your explanation should allow us to reproduce the problem so we can see it...
This is probably not something that should be run with _every_ version. But it totally makes sense as a manual thing we can run.