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
Right now SubGraph stores entities directly in app-db under keys that look like [:some-keyword some-key-value]. It makes it incredibly hard to look at app-db with the naked eye or with tools like https://github.com/flexsurfer/re-frisk. I think it would make sense to use a tree structure and store the entities like {:some-keyword {some-key-value some-value}}.
So instead of e.g. this
Another advantage of this approach is that it allows for fast querying of all entities of the same type (well, having the same ID attrs). That being said, I think it would also make sense to make it possible to rename the top-level key. It would also make it more simple to incorporate SubGraph into the existing app-dbs.
Right now SubGraph stores entities directly in
app-db
under keys that look like[:some-keyword some-key-value]
. It makes it incredibly hard to look atapp-db
with the naked eye or with tools like https://github.com/flexsurfer/re-frisk. I think it would make sense to use a tree structure and store the entities like{:some-keyword {some-key-value some-value}}
.So instead of e.g. this
it would be this
The text was updated successfully, but these errors were encountered: