Turned out that I was using an old node version(v11.9.0). Updated to

v12.15.0

and everything works now. Would suggest that you add checks for node version numbers

any news on the "prisma not running on netlify" issue? or a funky workaround? i was hoping to do a demo for my company in a few days showing the end to end but it's failing at the last hurdle 😞 here's a repo to reproduce the problem and the issue i opened with next.js on the off-chance it's with them found this in netlify's forums, which doesn't look like it was ever resolved

When creating compound index's is it possible to findUnique on that index? For example I create an index on firstName and lastName, I know the combination would be unique within a table. I'm pretty sure the prisma client used to do this but the types are not generated in the latest version.

Got it, needed

@@unique over @@index

Hello everyone! At the upcoming Prisma Enterprise Event, Pete Hunt, Software Engineer at Twitter will join Søren Bramer Schmidt, CEO of Prisma to explore the evolution of application data platforms at Facebook and Twitter and shed light on the architectural foundations that enable such companies to appease the need for scalability, productivity, and security. I highly recommend checking it out! You can still register here.

Hey folks--I have a typescript repo that fails on tsc compilation with type errors. When I run

sls package

with your typescript plugin, however, it just logs those errors, but continues on its merry way. How do I configure the plugin to fail

sls package

on typescript compilation errors/warnings?

Hey all, not sure if this is the place to post this, as it's about the nexus-prisma plugin, but I'm having trouble getting the

root

object passed into my Nexus resolvers to contain my relation fields from Prisma. ie, imagine this as a resolver for

tableA

t.field('tableBFoo', {
      type: 'DateTime',
      async resolve(root, _args, { prisma }) {
        const valueB = prisma.tableB.findUnique({
          select: {
            foo: true,
      },
      where: {
        objectId: root.tableB.objectId,
      },
    })
    return valueB.foo
  },
})

root.tableA

comes up null in this example. Not sure if this translates exactly, haven't tried it out, but the model for the above, if done the same way that we have it, should look like this:

model TableA {
  objectId    String @id
  tableBId    String @map("tableB")
  tableB      TableB? @relation(fields: [tableBId], references: [objectId])
  
}

model TableB {
  objectId    String @id
  foo         String
}

I know what we're doing there is pretty weird, i.e., using the name we want for the relational field for the ID in our database...We're working with (and trying to replace) a legacy system, but we would prefer to use the names as expected. Is there a way to achieve this?

I’ve worked though the entire React + Apollo Tutorial. I’m having a few issues around subscriptions. I notice on the page Realtime Updates with GraphQL Subscriptions in the second code block there is a variable

link

that is defined but never used? Did I miss something earlier or is something missing here? https://www.howtographql.com/react-apollo/8-subscriptions/

Hi...looking for some guidance here. Based on https://www.prisma.io/docs/guides/general-guides/database-workflows/sql-views-postgres#5-manually-add-the-draft-view-to-the-prisma-schema I added my view as a model in the Prisma schema. In the future if I add another table in my schema, I want to continue using

migrate

to be able to create the table. Is it possible to skip creation of certain models through

migrate

because then

migrate

will try to create a table with the name of the view that I created.

Hey, I would need 2 minutes help please. How would I adjust this schema to have a family with Users[] and a familyOwnerId with the User?!?

Hi, I am trying to start using

prisma migrate

with an existing DB (without resetting/losing my data), and finding the docs quite confusing -> https://www.prisma.io/docs/guides/application-lifecycle/add-prisma-migrate-to-a-project#baseline-your-production-environment It suggests using

prisma migrate dev

to establish a new migration history, but this tries to run a migration -- and fails, saying it's out of sync. Anyone able to show me the way? 🙏

Hello, what is the best way to overcome

text

column length limits? Prisma seems to set it to 191, without any way to specify in the schema, and I need much longer for some columns.

If I extend the length directly (with MySQL) -- then next migration it says the schema has drifted, so I feel it may not be the best thing to do

If I’m using Prisma in two services, same schema same db, what do I do if I don’t want to build a monorepo?

Do I just copy and paste schema/migrations each time I make a change?

I've been trying to figure out why the datasource isn't working for a couple of hours now. I changed from sqlite to postgres, and even though I lost all the data, prisma is now storing new records inserted by prisma studio somewhere. But it's not storing them in the postgres db

I've regenerated the client, run db push, done a bunch of stuff already. I run this script:

const { PrismaClient } = require('@prisma/client');
const prisma = new PrismaClient();
async function main() {
  const result = await prisma.mymodel.findMany({})
}

And I get the data that I inserted through prisma studio, but it's not the data in my postgres db, and it's not coming from the old sqlite one either as I've removed it

My schema is

datasource db {
  provider = "postgresql"
  url      = "<postgresql://postgres@localhost/mydb>
}

turning debug logging also gives me:

prisma:info Started http server on <http://127.0.0.1:59079>
prisma:info Fetched a connection from the pool

I have no idea what this server is supposed to be

The generated query:

prisma:query SELECT "public"."MyModel"."id", "public"."MyModel"."name" FROM "public"."MyModel" WHERE 1=1 OFFSET $1

what is this

public.

prefix

gah.. figured it out. The table names are case-sensitive, and I had actually migrated my data from an old sqlite database; the prisma client was seeing new data I had inserted through studio, but I was seeing the migrated data from the psql client because I wasn't double-quoting the table names

Has anyone managed to setup

prettier-plugin-prisma

? https://github.com/umidbekk/prettier-plugin-prisma

After doing

yarn add -D prettier-plugin-prisma

any other step/configuration needed?

Will the talks at the Prisma Enterprise Event of today be recorded and published? 😄

We're just about to start the *Prisma* *Enterprise Event*! 🎉 If you want to share in the fun, you can answer the questions we're asking the audience (and see the answers) here: http://sli.do/prisma

prisma.io is currently down due to a Netlify outage (https://www.netlifystatus.com/incidents/r2nqshvznvyj) As a workaround visiting www.prisma.io works Prisma staff with access to the DNS should update the

A

record following the advice in that incident report

Prisma is being used as a main ORM tool for new stunning boiler plate "Bedrock"

Are there any examples of someone building a shared Prisma client. To have a single schema be the source of all truth but be used through multiple repositories. Such as a private package that exports a Prisma client connected to the schema?