Prisma provides transactional guarantees for neste...
# prisma-whats-newb
Bro
03/27/2018, 3:49 PMPrisma provides transactional guarantees for nested mutations. If you wanted to do something like transfer 5 coins from player1 to player2, if player1 has 5+ coins, how would you suggest structuring this?
Bro
03/27/2018, 3:50 PMMy naive approach would be to create something like:
Copy code
type Player {
name: String! @unique
totalCoins: Int! @default(value: 0)
theBank: Bank!
}
type Bank {
name: String! @unique
player: [Player!]!
}h
harmony
03/27/2018, 3:52 PMwhat's the bank for?
b
Bro
03/27/2018, 3:54 PMIt really only provides edges between all players.
h
harmony
03/27/2018, 3:58 PMI mean that would probably be fine
harmony
03/27/2018, 3:58 PMjust have to write a resolver for the transaction
b
Bro
03/27/2018, 4:04 PMWould you still have a problem with double spending if you wrapped a query with a nested mutation as a resolver, but multiple requests hit at about the same time?
h
harmony
03/27/2018, 4:11 PMpossible
b
Bro
03/27/2018, 4:23 PMOk, so for this type of use case, it may be better to bypass Prisma and try to call a specific SQL query in the resolver.
Bro
03/27/2018, 4:25 PMAlso, thanks for helping me better understand what's going on.
h
harmony
03/27/2018, 4:29 PMprisma doesn't have atomic operations yet
b
Bro
03/27/2018, 4:36 PMI was reading the gh issues and Sorenbs mentioned something about rewriting multiple mutations into a nested one as a workaround for some problems. I was kind of thinking about ways to address this sort of problem.
2 Views