Update/db schema #320
Merged
Update/db schema #320
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- handle multiple users w/ same address - change primary address
3 tasks
|
@shanejearley - Need approval to merge this. |
DemogorGod
approved these changes
Apr 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@shanejearley - The primary purpose of this branch / PR is to make our PG schema more flexible in terms of handling the permutations (combinations?) of users and addresses (accounts as well) from a web3 perspective (e.g., previously, our schema was preventing two separate users from sharing an address in their list of accounts AND it was preventing a user from switching their primary address to another address). To achieve this, a simple PG generated/managed
idis used on both theusersandaccountstable, and a third composite table is used to associateuserswithaccounts.There are probably ways to optimize the
postgres.tsandschema.tsscripts, but focused on getting it working and figured we can settle on the general direction first before optimizations.We can defer to async review, but let me know if you'd like to review sync at any point.