timothé david
08/03/2021, 7:52 PMtimothé david
08/03/2021, 7:53 PMtimothé david
08/03/2021, 7:53 PMprisma : 2.28.0
@prisma/client : 2.28.0
Current platform : debian-openssl-1.1.x
Query Engine : query-engine 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/query-engine-debian-openssl-1.1.x)
Migration Engine : migration-engine-cli 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine : introspection-core 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary : prisma-fmt 89facabd0366f63911d089156a7a70125bfbcd27 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash : 89facabd0366f63911d089156a7a70125bfbcd27
Studio : 0.417.0
timothé david
08/03/2021, 7:58 PMtimothé david
08/03/2021, 8:00 PMTanmay Naik
08/08/2021, 6:28 AMError: Database error
11:57:09.507 Error querying the database: db error: ERROR: current transaction is aborted, commands ignored until end of transaction block
Any direction to solve this would be very helpful!Mischa
08/09/2021, 6:44 PMNico Domino
08/15/2021, 4:23 PM@relation (fields:..
Part refers to the newly refactored Int[]
field.
I guess my question is, is this even possible in Prisma? I've looked through the docs many times and only found reference to traditional many-to-many relationships with an intermediate tableTyler Matteo
08/16/2021, 3:17 AMAlex
08/17/2021, 1:39 AMjames tan
08/17/2021, 9:20 AMMischa
08/24/2021, 11:39 AMBrian Anglin
08/25/2021, 8:18 PMnapi
cut our p95 latency of a hot endpoint from ~800ms to around ~200ms. We're going to add actual caching to speed this up even more but was really scratching my head as to why performance was so poor for what felt like relatively light queries. This seemed to be like a pretty easy fix 🤷Pieter
08/26/2021, 12:56 PMAndre Landgraf
08/27/2021, 2:10 PM_count
currently broken for mongodb? It does not work for me, I just want to confirm, it’s not my query but a general problem? 🙂Alex
08/28/2021, 3:13 AMAndre Landgraf
08/28/2021, 6:38 PMMischa
08/29/2021, 10:43 AMMischa
08/29/2021, 10:44 AMnpx prisma generate
with the appsync plugin in the docker environmentKyle (TechSquidTV)
08/29/2021, 5:32 PMtype T_User {
id: ID!
name: String!
email: String
oauth_token: String
oauth_token_secret: String
}
input New_T_User {
name: String!
email: String
oauth_token: String
oauth_token_secret: String
}
...
type mutation {
create_t_user(input: New_T_User!): T_User!
update_t_user(input: Update_T_User): T_User
delete_t_user(id: ID!): T_User
}
Now, I am creating the function which will create a new user but I am running into this typing issue. This comes from the area of the tutorial headed with Adding post service
// Create a new user
async createUser(newUser: New_T_User): Promise<T_User> {
return this.prisma.t_user.create({
data: newUser
})
}
data
here is reporting an error as New_T_User
is not assignable.
full error:
Type 'New_T_User' is not assignable to type '(Without<t_userCreateInput, t_userUncheckedCreateInput> & t_userUncheckedCreateInput) | (Without<...> & t_userCreateInput)'.
Type 'New_T_User' is not assignable to type 'Without<t_userUncheckedCreateInput, t_userCreateInput> & t_userCreateInput'.
Type 'New_T_User' is not assignable to type 't_userCreateInput'.
Property 'email' is optional in type 'New_T_User' but required in type 't_userCreateInput'.ts(2322)
So here we see that email
is optional in New_T_User
, which, is expected. But it is somehow required in 't_userCreateInput'.ts
< im not sure exactly where this file is But I assume it comes from the generated prisma client. In my generated graphql.js file we can see email is an optional and nullable string
export class New_T_User {
id: string;
name: string;
email?: Nullable<string>;
}
Any help is appreciated thank you.Nditah Samweld
08/31/2021, 7:40 AMError: Generator at prisma-dbml-generator could not start:
/bin/sh: 1: prisma-dbml-generator: not found
Ubuntu 18, Node 14
prisma : 2.30.2
@prisma/client : 2.30.2
Current platform : debian-openssl-1.1.xGautam Paranjape
08/31/2021, 7:59 PMconst result = await db.package.findMany({
where: {
body: {
search: "test",
},
},
});
However, it’s throwing me an error, and I don’t know why. I have fullTextSearch enabled as a preview feature, and I even tried wiping node_modules & re-installing, and re-running npx prisma generate
.Pascal Sthamer
09/01/2021, 3:48 PMSahil Lavingia
09/01/2021, 7:07 PMSahil Lavingia
09/01/2021, 7:27 PMPrisma schema loaded from prisma/schema.prisma
Error: TypeError: Cannot read property 'engineType' of undefined
at getClientEngineType (/Users/sahil/code/loot-tme/node_modules/@
Hector
09/03/2021, 6:40 PMschema.prisma
file and the nexus code which generates the schema.graphql
file. How do I make Prisma use the file generated by Nexus to generate the Client and push changes to the DB? Thanks for the help.Kyle (TechSquidTV)
09/04/2021, 1:37 PMGautam Paranjape
09/04/2021, 5:39 PMChris
09/07/2021, 12:47 PM$queryRaw
which sums over various values in a Decimal column. The result incorrectly comes back as 337.40000000000003 instead of 337.4. The incorrect value is the same as what you would get back summing all the values in javascript. If I perform a similar query via the prisma client (without it being a raw query), the value is correctly represented as a Decimal. How can I get the correct Decimal value like this in a raw query? I've tried prismaClient.$queryRaw<Decimal[]>
but this does not helpChris
09/07/2021, 6:32 PMqueryRaw
as though the values were floats