[Documentation] Example schema for cockroachdb is not working

Bug description

In the docs with cockroachdb selected (https://www.prisma.io/docs/getting-started/setup-prisma/start-from-scratch/relational-databases/using-prisma-migrate-typescript-cockroachdb)

This is the example schema… which does not work The `autoincrement()` default function is defined only on BigInt fields on CockroachDB. Use sequence() if you want an autoincrementing Int field.

model Post {
  id        Int      @id @default(autoincrement())
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  title     String   @db.VarChar(255)
  content   String?
  published Boolean  @default(false)
  author    User     @relation(fields: [authorId], references: [id])
  authorId  Int
}

model Profile {
  id     Int     @id @default(autoincrement())
  bio    String?
  user   User    @relation(fields: [userId], references: [id])
  userId Int     @unique
}

model User {
  id      Int      @id @default(autoincrement())
  email   String   @unique
  name    String?
  posts   Post[]
  profile Profile?
}

I found examples like below, but what is the correct way for a classic autoincrement with cockroachdb ?

model Question {
  id        String   @id @default(cuid())

How to reproduce

Try the example schema with provider = "cockroachdb"

Expected behavior

Working autoincrementing id field. Correct documentation.

Prisma information

Environment & setup

• OS:
• Database:
• Node.js version:

Prisma Version

[janpio]

Fundamentally, yes - see https://www.cockroachlabs.com/docs/v21.2/sql-faqs#how-do-i-auto-generate-unique-row-ids-in-cockroachdb and related documenation from CockroachDB.

We are currently re-investigating this and might suggest different defaults for primary key columns (you might notice that our current choice does not necessarily represent best practices as communicated by CockroachDB itself) - but for now this works.

[erSitzt]

I switched back to Int with sequence, that way i did not have to change/cast/convert anything for the other frameworks that ran into the JSON Stringify errors…

I think there should just be a note that there are still issues around in dealing with BigInt and maybe a hint for Int with sequence if someone wants something similar to a classic autoincrement id.