Hi! Did anyone get this error when starting a docker image? My introspection query works correctly generating my datamodel.prisma well, but then it's reporting this error when it's initializing and my playground doesn't show any query/mutation.

Is you underlying database uses BigInts ?

Ok, I will wait. And yes, it uses bigints, in a few tables.. But only show this error in one table, not in the others. I don't know what is generating this -5 type..

I think you should open a new issue around this with a small repro(just export SQL commands to bootstap for your database). That way we can fix this and add this use case in upcoming introspection improvements

Ok, I will open it in a few minutes. But yes, you're right, if I change bigint to integer works perfectly.

Hello! A short example so we can reproduce this would be indeed nice. 🙂 There were some fixes regarding Bigint support recently. Not related to introspection as far as I know. @tim2 knows more.

This is a bug in the server code.

Hi @ejoebstl, here in my third post there is the creation DDBB script with this bigint issue. https://github.com/prisma/prisma/issues/4019 @Harshit created a reproduction for

prisma introspect

but it's the same code here. https://github.com/pantharshit00/prisma-issue-4019