Conversation
…on API Rework the database layer to behave as a simple persistence backend without embedded business logic. Key changes: - open the database connection once during application startup - reuse the active connection across the application - remove database path handling from the database implementation - introduce a context-based transaction helper ensuring automatic rollback on failure Legacy code remains temporarily in the repository to avoid CI breakage during the transition.
Replace the initial single-table layout with a normalized multi-table schema. The new schema separates the data model into multiple dedicated tables to improve structure, extensibility and long-term maintainability.
Update the CLI initialization process to use the new database schema and database root functions.
8b565ed to
ee12061
Compare
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
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.
This change introduces a new database architecture.
Highlights:
Legacy database code remains temporarily to avoid CI breakage during
the migration phase.
Implements: WP1
Tracking: #2