Andrew O.
09/13/2019, 11:06 PMScottAgirs
09/13/2019, 11:40 PMprisma.yml
file, when deploying to Zeit’s Now:
in development (localhost) [of course, haha] everything works as expected.
prisma.yml
datamodel: datamodel.prisma
endpoint: ${env:PRISMA_ENDPOINT}
secret: ${env:PRISMA_SECRET}
..
however, when deploying with now
the deployment times out with the following error:
/home/nowuser/src/node_modules/prisma-binding/dist/Prisma.js:41
T throw new Error(" *No Prisma endpoint found. Please provide the `endpoint` constructor option.* ");
T ^
T Error: No Prisma endpoint found. Please provide the `endpoint` constructor option.
T at new Prisma (/home/nowuser/src/node_modules/prisma-binding/dist/Prisma.js:41:19)
T at Object.<anonymous> (/home/nowuser/src/src/db.js:4:12)
T at Module._compile (module.js:652:30)
T
T at Module.load (module.js:565:32)
T at tryModuleLoad (module.js:505:12)
T at Function.Module._load (module.js:497:3)
T at Module.require (module.js:596:17)
T at require (internal/module.js:11:18)
T at Object.<anonymous> (/home/nowuser/src/src/index.js:3:12)
T [nodemon] app crashed - waiting for file changes before starting...
T More details: <https://err.sh/now-cli/no-open-port-found>
T signal: 9
T npm start
and a now.json:
{
"version": 1,
"build": {
"env": {
"DEV_FRONTEND_URL": "777",
"FRONTEND_URL": "777",
"PRISMA_ENDPOINT": "777",
"PRISMA_SECRET": "777",
"APP_SECRET": "777",
"STRIPE_SECRET": "777",
..
}
}
}
Any ideas fellow fellasz?Joey
09/14/2019, 12:48 AMVirgil Dinu
09/14/2019, 6:49 AMVirgil Dinu
09/14/2019, 8:23 AMTomHage
09/14/2019, 5:29 PMCarl Bowen
09/14/2019, 11:37 PMMarciano
09/15/2019, 8:04 PMError: Cannot return null for non-nullable field Log.id.
. Googled already to find an answer but I can't seem to find a solution. Does somebody have an idea what it could be? This is my code:
Query resolver:
const Query = {
async logs(parent, args, ctx, info) {
const logs = await ctx.db.query.logs();
return logs;
}
};
module.exports = Query;
schema.graphql
input LogInput {
name: String!
date: DateTime!
}
type Mutation {
createLog(data: LogInput): Log!
}
type Query {
logs: Log
}
datamodel:
type Log {
id: ID! @id
name: String!
date: DateTime!
}
Jack Hollis-London
09/15/2019, 11:42 PMMartí Crespí
09/16/2019, 6:21 AMdocker-compose.yml
file the option migrations
to false, but it's doing all changes according to my datamodel.prisma, I want to do my changes in DDBB directly and when I deploy my server it should check if the datamodel is ok with my DDBB. I'm using 1.34.5
version.koufatzis
09/16/2019, 8:06 AMprisma deploy
but it seems that the new fields I added in the datamodel.prisma
are not being deployed to the service. Because after running prisma import
command following issues are being logged:```
"The model XXX with id ZZZ has an unknown field 'YYY' in field list.",
```
Is there anything I need to be aware of about prisma deploy
?deactivateduser
09/16/2019, 12:50 PMJosef Henryson
09/16/2019, 4:48 PMCorey Snyder
09/16/2019, 5:12 PMImages
has a product: FlightControler
attribute. I was trying to figure out how I could link my Images to other product types and really couldn’t figure it out. You can’t do product: [FlightControllers, Motors, Battery]
, you have to give it a single Type to create a relationship to. So with this model, I think I can link all my other tables with product: Product
and then the product can then link to all of the product types. Thoughts?Corey Snyder
09/16/2019, 11:26 PMMichael Feldstein
09/17/2019, 4:09 AMToni Bennet
09/17/2019, 2:43 PMHays Clark
09/17/2019, 7:45 PMAndrew O.
09/17/2019, 8:23 PMAdam
09/18/2019, 12:49 AMAdam
09/18/2019, 12:49 AMAdam
09/18/2019, 12:52 AMThor Mengkheang
09/18/2019, 6:42 AMprisma-binding
like in the document https://www.prisma.io/docs/prisma-client/basic-data-access/reading-data-JAVASCRIPT-rsc2/#aggregations
await prisma.customersConnection().aggregate().count()
Jack
09/18/2019, 3:28 PM@rename
directive still working or no? It prints promising output in the terminal, but nothing actually changes in the DB...
It seems to be just when renaming types - renaming a field seems to work fine.Kimble
09/18/2019, 11:37 PMCameron Gorrrie
09/19/2019, 12:49 AMtype Cart {
id: Int! @id
sessionId: String! @unique
user: User!
items: [CartItem!]!
createdAt: DateTime! @createdAt
updatedAt: DateTime! @updatedAt
}
I want to upsert a cart given a sessionId and userId, but the autogenerated client doesn't have that capability (only id
and sessionId
are available). How could I go about this with the client, or am I going to have to dip into SQL?Adil
09/19/2019, 10:46 AMAdil
09/19/2019, 10:48 AMdoums
09/19/2019, 11:57 AMnexus-prisma
with prisma"1" support graphql subscriptions please ? Thanks !doums
09/19/2019, 12:03 PMnexus-prisma2
?