![]() the role field on User is of type String instead of Role, the enum definition for role is missing altogether.the jsonData field on User is of type String instead of Json.User ↔ Post is a m-n instead of 1-n relation.User ↔ Profile is a 1-n instead of 1-1 relation.There further are a number of inconsistencies which result in a less idiomatic/ergonomic Prisma Client API: no default value for the published field on Post.no default value for the role field on User.no auto-generated date values for the createdAt and updatedAt fields on Post.While this is already a valid Prisma 2 schema, it lacks a number of features that were part of its Prisma 1 equivalent: Switch around with the tabs in the code block to see examples of both: If you're using MySQL, it needs to define the value "mysql" in the provider field. ![]()
0 Comments
Leave a Reply. |