self explanatory
linear task
Details
Diff Detail
- Repository
- rCOMM Comm
- Branch
- master
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
I want to make sure @tomek takes a look since he has the most context on our MySQL setup
Overall looks good to me. Assume you've carefully tested that 42 chars is the right number?
I think that saving 2 bytes doesn't make any difference. What could make a difference is remembering in every place that we have to add 0x when reading from the db and removing it when writing. So for me we should keep it to make it more maintainable.
run keyserver & watch it migrate
It's also a good idea to check if creating an empty db also works correctly.
keyserver/src/database/migration-config.js | ||
---|---|---|
72 | Shouldn't matter too much, but it's a good practice to make code idempotent if possible: so in this case ADD COLUMN IF NOT EXISTS would be slightly better. |
I see 0x as a purely visual treatment, so I would prefer to have that handled by the UI.
It's also a good idea to check if creating an empty db also works correctly.
@derek can you amend your Test Plan to cover that please?
keyserver/src/database/migration-config.js | ||
---|---|---|
72 | Good call. This is something we probably should've learned from D5521 |
all the frontend clients (wagmi, rainbowkit, even alchemy) give us the address with the 0x prefixed. i agree with tomek, it feels like a lot of roundtripping to add & remove it just for db writes to save a couple bytes
Okay, the length of the field doesn't really matter. I won't block you on this, but it seems kinda wasteful to me