Add SQLite/SemSQL export format #1148
Merged
Conversation
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
Make sure that * sqlite3 (Debian package), * semsql (Python package), * rdftab (custom-built from source), * and Relation-Graph (downloaded as is) are all available in ODKLite, rather than only in ODKFull. This is so that a standard release pipeline still only requires ODKLite, even if the project is configured to produce SQLite/SemSQL files.
Support the production of release artefacts in SQLite/SemSQL format. This requires a CSV-formatted list of prefixes, so if the project is configured to use a global context, we derive the CSV from it. Otherwise, we let `semsql` use its builtin prefix list.
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 is exactly the same PR as #1147, just without the last commit which enabled SQLite/SemSQL export by default on all repos.)
This PR adds
dbas a new export format for release artefacts.A
.dbfile is a SQLite3 file containing a SemSQL representation of the release product.All tools needed to build SQLite3/SemSQL files (
semsql,rdftab,sqlite3, andrelation-graph) are moved from ODKFull to ODKLite, so that the standard, ODK-generated workflows still only require ODKLite. This increases the size of ODKLite from ~1.34GB to ~1.5GB (compared to ~3.06GB for ODKFull).If the project is configured to use a global prefix context (
use_context=true), the same context (converted from JSON to CSV) is used when building the SemSQL files. Otherwise, we letsemsqluse its built-in list of prefixes.closes #1142