Use object level versioning
This changes the global verioned object upgrade table to per-object upgrade tables, necessitating a version being sent to the get/set calls. It's not pretty but we decided it would have better flexibility moving forward and could be cleaned up in the future.
Showing
- storage/auth/sentRequest.go 6 additions, 3 deletionsstorage/auth/sentRequest.go
- storage/auth/store.go 2 additions, 2 deletionsstorage/auth/store.go
- storage/cmix/key.go 3 additions, 3 deletionsstorage/cmix/key.go
- storage/cmix/store.go 2 additions, 2 deletionsstorage/cmix/store.go
- storage/conversation/partner.go 3 additions, 3 deletionsstorage/conversation/partner.go
- storage/e2e/relationship.go 4 additions, 3 deletionsstorage/e2e/relationship.go
- storage/e2e/relationshipFingerprint.go 6 additions, 3 deletionsstorage/e2e/relationshipFingerprint.go
- storage/e2e/session.go 7 additions, 6 deletionsstorage/e2e/session.go
- storage/e2e/session_test.go 7 additions, 7 deletionsstorage/e2e/session_test.go
- storage/e2e/stateVector.go 3 additions, 3 deletionsstorage/e2e/stateVector.go
- storage/e2e/store.go 2 additions, 2 deletionsstorage/e2e/store.go
- storage/e2e/store_test.go 1 addition, 1 deletionstorage/e2e/store_test.go
- storage/partition/multiPartMessage.go 4 additions, 3 deletionsstorage/partition/multiPartMessage.go
- storage/partition/multiPartMessage_test.go 3 additions, 3 deletionsstorage/partition/multiPartMessage_test.go
- storage/partition/part.go 3 additions, 3 deletionsstorage/partition/part.go
- storage/partition/part_test.go 2 additions, 2 deletionsstorage/partition/part_test.go
- storage/reception/identity.go 3 additions, 3 deletionsstorage/reception/identity.go
- storage/reception/registration_test.go 2 additions, 2 deletionsstorage/reception/registration_test.go
- storage/reception/store.go 13 additions, 9 deletionsstorage/reception/store.go
- storage/reception/store_test.go 2 additions, 2 deletionsstorage/reception/store_test.go
Loading
Please register or sign in to comment