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
All data database tables follow the wrong types for timestamps, chainIds and possible other numbers
Timestamps should be Unix seconds as bigint, matching what is on-chain.
ChainIds should be big int matching what is on chain
Any number, like hypercert ID parts, that could be a bigint (because on-chain) should be a big int
There's a hypercerts table in the data database but those aren't the actual hypercerts but only pointers, so should be at least something like hypercertIds. It became very confusing at multiple points during the refactor
Instead of performing complex joins to get the state of the hyperboard or collection, I propose to add views for hyperboards and collections
Iirc, we mostly use UUIDs as IDs but for some reason hyperboards/collections have numbers
@bitbeckers on discord