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

Cross collection transactions? #105

Open
delaneyj opened this issue Jan 7, 2024 · 1 comment
Open

Cross collection transactions? #105

delaneyj opened this issue Jan 7, 2024 · 1 comment

Comments

@delaneyj
Copy link

delaneyj commented Jan 7, 2024

Since its in-memory would it be possible to have single TX across multiple collections? For example in your grid/movement ecs example it would make sense to be able to update both as a single transaction.

Especially for ECS semantics a system generally has full control on the state and the TX semantics are at a different level.

@Dreeseaw
Copy link
Collaborator

I think allowing cross-collection transactions could be possible with some tweaks to the structure of the transaction pool, however, I feel like maintaining consistency in a collection across multiple cross-collection transactions would require a very pessimistic approach (and therefore not performant). We'd need something like timestamp-based concurrency control, or maybe a special copy-on-write implementation for the columns.

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

2 participants