Skip to content

Conversation

@Sammster10
Copy link
Member

@Sammster10 Sammster10 commented Sep 12, 2025

The motivation behind this rewrite is simple. 1. static-data needs to be more flexible. 2. Delegating a lot of the heavy lifting to H2 makes this project much easier to maintain.

While #20 is not implemented directly, with the query builder we can support more flexible, map-like queries. i.e WHERE user.fav_color = ?. key being fav_color, value being user.

Sammster10 and others added 17 commits November 12, 2025 22:05
- previously each insert context only knew about itself. this lead to statements being generated to satisfy dependencies. this is fine, however in the context of a batch, the statement may already be present. this change makes every statement aware of every other statement within the batch
all data classes must be loaded, then #finishLoading() should be called. this is what syncs the data from the source rather than doing multiple syncs
this is not needed and introduced lots of issues
…enient, it can be misleading. For example, do i update the values in the referenced table, or the referring table?
…transaction has been committed.

this also means that update handlers are called instantly, and no longer require being submitted to another thread.
@Sammster10 Sammster10 closed this Dec 31, 2025
@Sammster10 Sammster10 deleted the h2 branch December 31, 2025 12:19
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

Successfully merging this pull request may close these issues.

Use H2 as internal cache Map-like data structure Improve deletion performance

3 participants