@id @unique on id error should be highlighted when creating schemas and db push should fail

Bug description

I noticed Prisma doesn’t reject or complain for error "@unique": Fields that are marked as id should not have an additional" until when the schema has been pushed to db then error would pop out in Prisma studio. I think this can improved by letting developer know before hand!

How to reproduce

example:

  model Payment {
  paymentId String   @id @unique
  date      DateTime @default(now())
  amount    Int
  success   Boolean  @default(true)
  order     Order[] 
                 }

with the schema, prisma db push is a success instead of failing because paymentId field has @id and @unique

Expected behavior

Prisma should report this error “@unique”: Fields that are marked as id should not have an additional" before prisma db push can be successful

Prisma information

Environment & setup

• OS: Mac OS
• Database: PostgreSQL
• Node.js version: v14.16.1

Prisma Version

prisma                  : 3.9.2
@prisma/client          : 3.9.2

[borngraced]

Ok…sorry, I’ve been away. I’m going to try to reproduce the error and share!

[janpio]

Fields that are marked as id should not have an additional @unique is not part of our codebase anymore, so we can close this issue. You probably had different versions running locally in some way, which meant that Studio used an older validation than the rest of the tooling.