batch updating... do I need the where: {...} part ...
# orm-helpz
zonofthor
05/02/2018, 9:09 AMbatch updating... do I need the where: {...} part if I want to update every row ? (nested update)
mutation($chocolateId: ID!) {
updateChocolate(
where: { id: $chocolateId }
data: {
sections: {
update: {
where: {--no filter here, update all--}
data: {title:null}
}}
}
) { id }
}
f
Fi1osof
05/02/2018, 9:26 AMYes, where is required, but you can pass empty object where: {}
All records will updated
z
zonofthor
05/02/2018, 9:32 AM"code": 3040,
"message": "You provided an invalid argument for the where selector on ChocolateSection.",
zonofthor
05/02/2018, 9:33 AMon Prisma... if that matters?
n
nilan
05/02/2018, 10:21 AMyou need to use updateMany.
z
zonofthor
05/02/2018, 10:26 AMbut I only want to update single root type (and many nested)... ?
n
nilan
05/02/2018, 10:30 AMah you're talking about inner updates. No, update accepts a list of objects instead
z
zonofthor
05/02/2018, 10:33 AMgotcha...
mutation($chocolateId: ID!) {
updateManyChocolates(
where: { id: $chocolateId }
data: {
sections: {
update: {
where: {}
data: {
handles: {
update: {
where: {}
data: {
input: {
update: {
value: null
}}}}}}}}}
) { count }
}
zonofthor
05/02/2018, 10:34 AMlong tail there... but this is pattern?
n
nilan
05/02/2018, 10:35 AMdo all nodes receive the same update?
nilan
05/02/2018, 10:35 AMor are some nodes getting other values than others
z
zonofthor
05/02/2018, 10:36 AMall nodes are nulled
zonofthor
05/02/2018, 10:36 AMvalue:null
n
nilan
05/02/2018, 10:37 AMnot sure if that's possible using updateMany off the bat, but you can try 🙂
nilan
05/02/2018, 10:37 AMif it's not possible, you need to do it like in your first version but instead of
update: { where:... }update: [{ where:... }, { where:... }, { where:... },...]z
zonofthor
05/02/2018, 10:39 AMno errors but values are unchanged
zonofthor
05/02/2018, 10:39 AMaha... I'll try the brackets
zonofthor
05/02/2018, 10:45 AMback to code 3040 error...
zonofthor
05/02/2018, 10:45 AM' mutation($chocolateId: ID!) {
updateChocolate(
where: { id: $chocolateId }
data: {
sections: {
update: [{
where: {}
data: {
handles: {
update: {
where: {}
data: {
input: { update: {value: null}}
}
}}}}]}}
) { id }
}'
n
nilan
05/02/2018, 10:46 AMthis where can't be {}.
z
zonofthor
05/02/2018, 10:46 AMbut how to update all rows then?
zonofthor
05/02/2018, 10:47 AMit only allows where: {id: "xxx"}
n
nilan
05/02/2018, 10:47 AMyup that's how you can do it.
z
zonofthor
05/02/2018, 10:47 AMbut it should update all (nested) rows ?
n
nilan
05/02/2018, 10:47 AMyou can also query the nodes first, then update them
z
zonofthor
05/02/2018, 10:47 AMcould you please tip me on that syntax?
zonofthor
05/02/2018, 10:58 AMpretty please, since I don't know how to query then update... just a newbie!
zonofthor
05/02/2018, 11:28 AMquery...update - you mean I could do that without roundtrip?
n
nilan
05/02/2018, 12:10 PMI provided as much input as I can at this point 🙂 If you want to, you can describe your situation in the Forum to find the best approach.
z
zonofthor
05/02/2018, 12:11 PMindeed - thank you, just I am not sure how to do a query...update in one mutation query, I´ll post to forums yes
n
nilan
05/02/2018, 12:11 PMoh, you can't. I talked about separate queries/mutations.
z
zonofthor
05/02/2018, 12:21 PMahh ok, thank you
zonofthor
05/02/2018, 12:21 PMguess it's time to dig in custom resolvers
2 Views