Kha
02/08/2021, 6:42 AMMykyta Machekhin
02/08/2021, 8:08 AMnpm i --save-dev prisma
npm i @Prisma/client
. But still have 2.15 version. Why can this happen?rahul
02/08/2021, 12:59 PMrahul
02/08/2021, 1:00 PMNatalia
John Peña
02/08/2021, 10:43 PMiamclaytonray
02/09/2021, 2:04 AMryan
02/09/2021, 4:30 PMcreateMany
method. The video will walk you through how to use it in the context of database seeding:
Prisma CLI
The second is about the package name change for the Prisma CLI. As you may have seen, you should install the CLI using the package of prisma
going forward. This video explains the details:
Martïn
02/09/2021, 10:20 PMJeff Barg
02/09/2021, 10:29 PMTarrence
02/10/2021, 3:52 AMTarrence
02/10/2021, 3:52 AMTarrence
02/10/2021, 3:53 AMtime out of range
Tarrence
02/10/2021, 3:53 AMdebug: 2021/02/10 03:51:57 prisma engine payload: `{"query":"mutation {result: executeRaw(query:\"UPDATE \\\"EventInstance\\\" SET \\\"start\\\" = date_trunc('day', \\\"start\\\") + CAST ($1 as time), \\\"end\\\" = date_trunc('day', \\\"end\\\") + CAST ($2 as time) WHERE \\\"eventId\\\" = $3\\n\\t\",parameters:\"[\\\"2021-02-08T04:00:00Z+00:00\\\",\\\"2021-02-08T05:00:00Z+00:00\\\",\\\"readily-illegally-upward-urchin\\\"]\",) }","variables":{}}`
Ralf Vogler
02/10/2021, 2:56 PMnow()
? Can't use @updatedAt
since there's nothing else to update. Currently I'm setting it to new Date()
but that comes from the client which might be not in sync with the server's time.Chase Roossin
02/10/2021, 11:54 PMPost
that has relationship to many Likes
- When retrieving many posts... what is the most efficient way to see how many likes its got and if you are on of those likes.
Seems like you would need several queries? Does anyone have an example of the most performant way to do this?Pedro Fellipe
02/11/2021, 12:26 AMMartïn
02/11/2021, 7:14 AMmxstbr
02/11/2021, 11:47 AMRalf Vogler
02/11/2021, 3:38 PMSébastien Dubois
02/11/2021, 4:08 PMDustin
02/11/2021, 5:24 PMChip Clark
02/11/2021, 5:26 PMIvan Lukianchuk
02/12/2021, 2:44 AMMaciek K
02/12/2021, 10:11 AMapp_1/prod
(The one we are migrating along with the one below)
• app_1/dev
(yes, im usually developing the app while accesing the remote prisma server, not localhost prisma)
• app_2/prod
(This one will probably stay forever on Prisma1)
My idea is to do the migration on app_1/dev
and if everything goes smooth, do the same on app_1/prod
My questions:
Is this a good approach, or should i try once more to recreate the prisma server on localhost?
And the most important question:
While doing migration work on the app_1/dev
schema, will the other schemas in db be affected by it? Will anything collide? What about the management
schema? Anything to worry here while doing the migration in that way?
Thanks!Leonard
02/12/2021, 9:09 PMYucheng
02/14/2021, 2:16 AMvnadygin
02/14/2021, 2:25 PMBradly Locking
02/14/2021, 11:04 PM