Jackson Malloy
02/19/2020, 7:23 AMyassine
02/19/2020, 12:01 PMOmar Nasr
02/19/2020, 9:03 PMBenjamin Wilson
02/20/2020, 3:03 AMERROR: No cluster could be found for workspace '*' and cluster 'default'
Ruhan Khandakar
02/20/2020, 4:42 AMRuhan Khandakar
02/20/2020, 4:43 AMNEED URGENT HELP
Victor Mukherjee
02/20/2020, 4:08 PMjohhansantana
02/20/2020, 8:37 PMOmar Nasr
02/20/2020, 10:47 PMTSVECTOR
and store in another column. Then create a index on that processed column. The issue with this solutions is inserts and updates will progressively get slower as the table gets larger, however for my use cases it works. SQL is contained in link
https://github.com/sara-sabr/ITStrategy/issues/806Natalia
02/21/2020, 10:20 AMtype Goal {
goalId: ID! @id
solutions: [Solution]
}
type Solution @embedded {
solutionId: ID! @id
name: String!
factsDelta: [FactsDelta!]!
}
type FactsDelta @embedded {
jsonPath: String!
jsonData: String!
}
These mutations execute without errors, field "name" on solutions is updated correctly, but updateMany and deleteMany on factsDelta do nothing, leaving factsDelta.jsonData untouched:
mutation {
updateGoal(
where: {
goalId: "5e4eb158857aba000744a8eb"
},
data: {
solutions: {
update: {
where:{
solutionId: "5e4eb87f857aba000744a902"
},
data:{
name: "this field is updated correctly"
factsDelta:{
updateMany:[
{
where: {
},
data: {
jsonData: "this isn't"
}
}
]
}
}
}
}
}
) {
goalId
solutions {
solutionId
name
factsDelta {
jsonPath
jsonData
}
}
}
}
mutation {
updateGoal(
where: {
goalId: "5e4eb158857aba000744a8eb"
},
data: {
solutions: {
update: {
where:{
solutionId: "5e4eb87f857aba000744a902"
},
data:{
name: "this field is updated correctly"
factsDelta:{
deleteMany:{
}
}
}
}
}
}
) {
goalId
solutions {
solutionId
name
factsDelta {
jsonPath
jsonData
}
}
}
}
While updateMany and deleteMany on solutions field works just fine:
mutation {
updateGoal(where: {
goalId: "5e4eb158857aba000744a8eb"
},
data: {
solutions: {
updateMany:{
where:{
},
data: {
name: "this field is updated correctly"
}
}
}
} ) {
goalId
solutions {
solutionId
name
factsDelta {
jsonPath
jsonData
}
}
}
}
ThanksJustin Prather
02/21/2020, 1:49 PMAlex Vilchis
02/21/2020, 2:39 PMAmaan Sayed
02/21/2020, 6:16 PMSamrith Shankar
02/22/2020, 1:28 AMRMCS
02/22/2020, 8:23 AMLars Ivar Igesund
02/22/2020, 11:34 AMLars Ivar Igesund
02/22/2020, 11:51 AMLars Ivar Igesund
02/22/2020, 11:51 AMlionbrahh
02/22/2020, 1:20 PMlionbrahh
02/22/2020, 1:27 PMMadison Haradine
02/22/2020, 5:47 PM$prisma deploy
isn't actually saving my changes after it updates them? https://stackoverflow.com/questions/60354928/prisma-isnt-applying-changes-after-prisma-deployJackson Malloy
02/22/2020, 6:44 PMMatti Joik
02/22/2020, 11:30 PMSamrith Shankar
02/23/2020, 1:08 AMError validating model "Task": Automatic related field generation would cause a naming conflict. Please add an explicit opposite relation field.
I don’t seem to understand what the explicit opposite relation field is
.Samrith Shankar
02/23/2020, 1:09 AMauthor User @relation(name: "taskAuthor", references: [id])
assignee User @relation(name: "taskAssignee", references: [id])
And it throws this error for assignee
Samrith Shankar
02/23/2020, 2:04 AMAshiqur Rahman
02/23/2020, 6:12 AMNick
02/23/2020, 11:16 AMyassine
02/23/2020, 11:36 PMProperty 'model' does not exist on type 'ObjectDefinitionBlock<"User">'.ts
yassine
02/23/2020, 11:36 PM