Raw query returning a bigint for an int field about prisma HOT 1 OPEN

Hey @iGarym, I took a quick look and was able to confirm the following data with the query and schema you provided!

[
  { id: 1n, name: 'folder-1', pid: 0n }
  { id: 2n, name: 'folder-2', pid: 0n }
  { id: 5n, name: 'folder-1-2', pid: 1n }
  { id: 7n, name: 'folder-2-2', pid: 2n }
]

So I took a quick look at the MySQL documentation and the problem here comes from it being an unsigned 32-bit value rather than a signed 32-bit value which gives it an upper range target of 4294967295 which is beyond the scope of js' 32-bit number. So this isn't a bug per se, it really should be a bigint.

I definitely see where the confusion comes from, however, we should probable have another addition in the table you mentioned that clarifies where unsigned integers land.

from prisma.