converged-database-lab: module 02 — Converged vs. Multi-Model (article 2 companion) - #5
Merged
Merged
Conversation
…converged-vs-multi-model Per-article companion module on its own branch (branch-per-piece), rehosted in the Oracle UMT Developer Hub layout under labs/converged-database-lab/.
Module map: 02 goes Live (3 proofs, 18 assertions; article link lands at publish); 01 counts corrected to 5 proofs / 20 assertions and linked to the published article. CI badge repointed from the pre-migration repo to this hub's converged-database-lab workflow.
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.
Merges the article-2 companion module into main ahead of the article's publication.
What's in it
modules/02-converged-vs-multi-model— 3 proofs, 18 assertions:01-survey-challenge.sql— the Lu & Holubová (ACM CSUR 2019) Fig. 1 multi-model challenge answered in one standard SQL statement (SQL/PGQ GRAPH_TABLE + SQL/JSON JSON_TABLE), asserting the survey's published result set exactly, plus one-plan EXPLAIN evidence.02-one-enforcement-domain.js— the same CHECK constraint rejecting an illegal write through the MongoDB-compatible API and through SQL ($sql), one enforcement domain.03-read-after-write-search.sql— committed row findable by CONTAINS in the next statement (SYNC ON COMMIT), read-after-write across a commit boundary.Validation: module runs green in the lab validator (fresh-container build); the path-scoped CI workflow covers it on this PR.
Note: the article-2 blog link in the module map lands at publish (article not yet announced).