Prisma1: The 'first' modifier is not working correctly in nested (one-to-many) nodes using PostgreSQL.

[ficolo]

Describe the bug
The 'first' modifier is not working correctly in nested (one-to-many) nodes using PostgreSQL.

To Reproduce
Steps to reproduce the behavior:

1. Init a prisma instance selecting the Docker local installation option with PostgreSQL as database
2. Deploy this datamodel User, University, Career datamodel

type User {
  id: ID! @unique
  name: String
  interestedIn: [University!]!
}

type University {
  id: ID! @unique
  name: String
  careers: [Career!]!
}

type Career {
  id: ID! @unique
  name: String
}

1. Load this data example-data
2. Try to get all the users, with all the universities they are interested in, but only including the first 10 careers for those universities

query{
  users{
    name
    interestedIn{
      name
      careers(first: 10){
        name
      }
    }
  }
}

Expected behavior
It should return the only user (username=Federico) with the three loaded universities with the first 10 careers for each university, but is only returning the first 5 careers for Harvard, the first 5 for Cambridge, and the all 3 careers for Oxford.

Screenshots

Versions (please complete the following information):

• OS: OS X High Sierra
• prisma CLI: 1.16.2
• Prisma Server: 1.6.2
  
  
  
  • DB: PostgreSQL 10.5
  
  

Additional context
I tried to reproduce this bug using MySQL and it works as expected.

[LawJolla]

Probably the same as https://github.com/prisma/prisma/issues/3040

[do4gr]

Thanks for this reproduction @ficolo, I can reproduce it and we'll release a fix shortly.

[do4gr]

We just released 1.16.4 which should fix this issue.

[ficolo]

Thanks!

I tested and it works as expected.