Nilan Marktanner
Nilan Marktanner
The proposal mentions --- To specify a unique constraint covering multiple fields, simply use the @unique directive instead of @index: ```graphql type User @model { id: ID! @isUnique name: String...
How will multi-field unique constraints be reflected in `where` input objects? Example schema: ```graphql type Post { id: ID! @unique title: String @unique(groups: [{name: "combined_title_and_slug", position: 0}]) slug: String @unique(group:...
I can confirm that this does not work as of now. Deploying this datamodel: ```graphql type User { id: ID! @unique name: String! ints: [Int!]! @default(value: "[1, 2, 3]") strings:...
Yes, a possible specification is being considered + discussed in detail here: https://github.com/graphcool/prisma/issues/1300
My bad 🙂 I'll open this issue again, thanks for the heads up @jvbianchi. @kieusonlam, the plan is to eventually bring back the evolution of the Prisma API into the...
Sure, that's a great point. You are connecting your database to Prisma, so you can also send raw queries there 🙂
The best workaround I'm aware of, is to order items client side 🙂
Thanks @stevewpatterson, this would be useful! Another use case: interface for `createdAt`/`updatedAt`
The `File` model could be pulled out as an interface. If you have relations between File and multiple other models, you currently have many `null` values.
Hey @ptpaterson, thanks so much for your feedback! This matter absolutely did not decrease in priority and is on our near-future roadmap together with #165. We're in the process of...