You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm working on satistics I'm realizing a lot of db model could use refactoring now that paid actions are pretty ubiquitous.
Something like a PaidAction table that's a parent of ItemAct, SubAct, etc. so it can include other things like buying CCs (needs its own special table otherwise), giving invite gifts (currently inferred), rewards, etc.
PaidAction {
type
state
cost
senderId
receiverId
paymentMethod
}
Then relevant rows in other tables (should they be needed) would belong to a PaidAction. This might make retries and other types of associations easier.
It's maybe not a high priority thing but it's longterm optimal afaict.
The text was updated successfully, but these errors were encountered:
As I'm working on satistics I'm realizing a lot of db model could use refactoring now that paid actions are pretty ubiquitous.
Something like a
PaidAction
table that's a parent ofItemAct
,SubAct
, etc. so it can include other things like buying CCs (needs its own special table otherwise), giving invite gifts (currently inferred), rewards, etc.Then relevant rows in other tables (should they be needed) would belong to a
PaidAction
. This might make retries and other types of associations easier.It's maybe not a high priority thing but it's longterm optimal afaict.
The text was updated successfully, but these errors were encountered: