feat: Add SQL event sourcing engine demonstrating database as events#7
Open
DLaneAtElekta wants to merge 1 commit intomasterfrom
Open
feat: Add SQL event sourcing engine demonstrating database as events#7DLaneAtElekta wants to merge 1 commit intomasterfrom
DLaneAtElekta wants to merge 1 commit intomasterfrom
Conversation
Implements Prolog predicates simulating a SQL database engine where all operations (INSERT, UPDATE, DELETE) are stored as events. The current state is derived by replaying events - demonstrating how SQL databases are fundamentally event sourcing systems. Features: - CQL-style term format (table :: [col-Var, ...]) - DDL operations (CREATE TABLE, DROP TABLE) - DML operations with full event capture - Transaction support with rollback - State projection by event replay - Complete audit trail capability
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements Prolog predicates simulating a SQL database engine where
all operations (INSERT, UPDATE, DELETE) are stored as events. The
current state is derived by replaying events - demonstrating how SQL
databases are fundamentally event sourcing systems.
Features: