feat:Add experimental sqlite-fts skeleton (not C3) - #12
Open
guozhihao-224 wants to merge 1 commit into
Open
Conversation
…ch pits. Port Analyzer v1 and a node:sqlite runtime that can remember and FTS-search self-created databases, while refusing unstamped Python-like files and without claiming C3 or shared-database writes.
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.
Summary
Add a Node
node:sqlitepersistence skeleton so we can test whether theTypeScript port hits fatal language-switch pits (Analyzer v1, INTEGER,
FTS projection, CAS, and refusing unstamped databases).
This is an experimental self-created-database path only. It does not
implement the shared-schema gate in #3, does not write existing Python
databases, and does not claim
sqlite-fts/ C3.Profile and parity
sqlite-fts(experimental skeleton only; not a product profile claim)(experimental DB allowed; no shared-write / C3 claim). Analyzer identity
powercontext.analyzer.v1.Checklist
contract/orconformance/snapshotspackages/protocol/src/generated(ADR 0002 experimental DB;
SHARED_DATABASE_WRITES_ALLOWED = false)Test plan
Optional Analyzer oracle (pinned oceanbase/powercontext at 733e4bf6b378785e76274ff07632029c699ecb09, not PowerMem):
Out of scope