docs: document SQLite as a supported Ecto backend#7
Merged
Conversation
The Ecto persistence adapter is backend-agnostic (standard column types, runtime-bound table, no DB-specific SQL) and SQLite is the backend the test suite runs against, but the README only mentioned Postgres. Note :ecto_sqlite3 in the deps comment and add a short backend-agnostic note to the Ecto section.
Ch4s3
added a commit
that referenced
this pull request
May 23, 2026
…nown parents
- memoize each flag's resolved state within a single enabled?/2 call, so a shared
(diamond) prerequisite graph is evaluated once instead of O(2^depth) re-walks
- propagate cycles as a distinct :cycle status so they fail closed uniformly,
including required:false edges (which a plain false previously satisfied, making
a mutual requires:{_,false} cycle report both flags enabled)
- treat a non-atom (unresolved) parent name as not-met (fail closed)
Addresses adversarial findings #5, #7, and the prerequisite half of #4.
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
1 participant
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.
The Ecto persistence adapter is backend-agnostic (standard column types, runtime-bound table, no DB-specific SQL) and SQLite is the backend the test suite runs against, but the README only mentioned Postgres. Note :ecto_sqlite3 in the deps comment and add a short backend-agnostic note to the Ecto section.