Timeless and log_tick cannot coexist
#2074
Assignees
Labels
Comments
teh-cmc
added
💬 discussion
🏹 arrow
5 tasks
5 tasks
teh-cmc
added a commit
that referenced
this issue
Apr 5, 2024
Introduces the concept of static data into the data APIs. Static data is a on a per-entity per-component basis. If it exists, it unconditionally shadows any temporal data of the same type. It is never garbage collected. When static data is returned, it is indicated via `TimeInt::STATIC`. The terminology has been normalized all over the place: data is either static or temporal, and nothing else. Static data cannot have more than one cell per-entity per-component. Trying to write more than one cells will trigger last-write-wins semantics, as defined by `RowId` ordering. Timeless fallbacks just don't exist anymore, which simplifies out _a lot_ of code in the datastore and query cache. Note: static data is in many subtle ways incompatible with our legacy InstanceKey-based model, which results in a couple hacks in this PR. Those hacks will be gone as soon as the new data APIs land and instance keys go away. - Fixes #5264 - Fixes #2074 - Fixes #5447 - Fixes #1766 --- Part of a PR series that removes the concept of timeless data in favor of the much simpler concept of static data: - #5534 - #5535 - #5536 - #5537 - #5540
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding a timeline to something timeless would suddenly make it not timeless... so for now it cannot even have a tick :/
This is a fundamental limitation of our current timeless model, which acts as a fallback but not really...
The text was updated successfully, but these errors were encountered: