Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Hierarchy/Definition universal behavior for get_ts and get_props #263

Open
rburghol opened this issue Jun 2, 2021 · 0 comments
Open

Comments

@rburghol
Copy link
Contributor

rburghol commented Jun 2, 2021

  • individual entity types (ts, props, features, vardefs) have the master model of their type, retrievable via method table_def()
  • datasource instantiates its tables for props, ts, features, etx. on creation by creating an instance of each entity type and calling table_def()
  • each entity that is instantiated instantaites it's own copy of ts and props,l by calling table_def() for those types as well and can therefore leverage tsvalue_search() and propvalue_search() in same was as datasource can.
  • in this way the search methods for an individual entity operate identically to those for the datasource and individual entities
  • todo: have individual entities like features store a copy of props and tsvalues
  • Force_refresh = false, local, or remote to allow persistence of local state. ie, if ts/prop not on an entity, always check the ds local, and check the remote if not on ds local. But if ts/prop is on the entity, only check ds local if firce_refresh = local, and only check remote if force_refresh = remote
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant