PyPI - mainsequence-metatable - Versions diffs - 0.1.10.dev21__tar.gz → 0.1.11.dev22__tar.gz - Mend

@@ -38,6 +38,20 @@ storage isolation. Require `local_mode: true`; after initialization also require
 stop the mutating work and select Local in Settings or restart with `serve --local`.
 Do not retry against automatic hosted discovery when a local connection fails.
+## One local runtime per laptop
+The local runtime is a single SQLite file, `~/.local/share/metatables/metatables.sqlite`
+by default, shared by every project, checkout and branch on the machine. Each project
+records it under `local` in its `.local/runtime-data-sources.json`.
+- A checkout that ran an earlier MetaTables release may still have its own
+  per-checkout file saved there; upgrading does not move it. To join the shared
+  runtime, select the shared file in Settings. The old file's tables are not copied:
+  run the application's migrations and fixtures again, and leave the old file in place.
+- The shared runtime is at the newest system migration any project applied. If
+  status reports an unsupported revision, upgrade the application's
+  `mainsequence-metatable` instead of selecting another database.
 ## Establish the development loop
 1. Work in the consuming application's Git checkout, with its commit and origin
@@ -120,9 +134,10 @@ or idempotent behavior. For a persistence claim, restart and read existing rows
 before seeding again. Recheck runtime state after any restart or mode/source change;
 do not switch modes while tests or producers are running.
-Local storage persists across launches and Git branches of the checkout. A new
-branch does not create a fresh test database. Use identifiable fixtures and clean
-up only the rows owned by the test. When a fresh database is necessary, select a
+Local storage persists across launches, and other projects' tables and fixtures share
+the same runtime. A new branch or project does not create a fresh test database. Use
+identifiable fixtures in the application's own namespace and clean up only the rows
+owned by the test. When a fresh database is necessary, select a
 separate temporary SQLite file through Settings and initialize it explicitly;
 restore the previous selection afterwards. Do not delete or replace a developer's
 existing database just to obtain a clean test run.

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.10.dev21
+Version: 0.1.11.dev22
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

@@ -104,16 +104,25 @@ The default file is:
 The local runtime is one per laptop: every checkout, repository and branch uses the
 same file. `METATABLES_LOCAL_STORAGE_DIR` changes its directory. Settings can
-configure another absolute SQLite file. The local DataSource UID derives only from
-the file location. The selected file is
-stored under the single `local` entry in `.local/runtime-data-sources.json`. Branch
-changes and restarts reuse it, its credentials and its DataSource UID. Git context
-still describes the running code; changing that context requires restarting the API.
-Existing files retain their paths, storage markers and IDs. A single legacy saved
-file is adopted intact and its selection is rewritten to `local`. When multiple
-legacy files exist, choose the intended file in Settings; startup does not guess,
-merge catalogs or create an empty replacement. Old unselected files are preserved.
+configure another absolute SQLite file. A new file's identity derives from its
+location; an existing file keeps the identity recorded in its scope marker, so a file
+moved together with its marker keeps its DataSource UID and run logs. The selected
+file is stored under the single `local` entry in `.local/runtime-data-sources.json`.
+Branch changes and restarts reuse it, its credentials and its DataSource UID. Git
+context still describes the running code; changing that context requires restarting
+the API.
+Existing files retain their paths, storage markers and IDs. A checkout that saved a
+per-checkout file under an earlier release keeps using it after an upgrade; select
+the shared file in Settings to join the laptop runtime. Its tables are not copied, so
+run the application's migrations and fixtures again. A single legacy saved file is
+adopted intact and its selection is rewritten to `local`. When multiple legacy files
+exist, choose the intended file in Settings; startup does not guess, merge catalogs
+or create an empty replacement. Old unselected files are preserved.
+Every project opening the shared file needs a MetaTables release that includes the
+file's system migrations. An older client reports an unsupported revision; upgrade
+its `mainsequence-metatable` rather than selecting another database.
 The runtime source remains fixed while active. The Data Sources page displays it but
 cannot retarget, disable or delete it. Source selection belongs to Settings, where the

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "mainsequence-metatable"
-version = "0.1.10.dev21"
+version = "0.1.11.dev22"
 description = "Main Sequence MetaTables Python client and standalone API"
 readme = "README.md"
 requires-python = ">=3.13"

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence-metatable
-Version: 0.1.10.dev21
+Version: 0.1.11.dev22
 Summary: Main Sequence MetaTables Python client and standalone API
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: MIT

@@ -165,7 +165,12 @@ def select_local_workspace(
         .resolve()
     )
     # The local runtime belongs to the laptop, not to a checkout: every project
-    # shares this file, and its identity follows only the file location.
+    # shares this file. A new file's identity follows its location; an existing
+    # file keeps the identity in its scope marker, so a moved runtime stays itself.
     path = root / "metatables.sqlite"
-    uid = uuid5(NAMESPACE_URL, "metatables:local-runtime:" + str(path))
+    marker = _read_marker(path.with_name(path.name + ".metatables-scope.json"))
+    if marker and marker.get("purpose") == "runtime":
+        uid = UUID(marker["workspace_uid"])
+    else:
+        uid = uuid5(NAMESPACE_URL, "metatables:local-runtime:" + str(path))
     return LocalWorkspace(uid, source, path)

@@ -1,6 +1,7 @@
 """One local runtime per laptop survives checkout and branch changes without platform sources."""
+import json
 from dataclasses import replace
-from uuid import uuid4
+from uuid import uuid4, uuid5
 import pytest
 from mainsequence.code_repository_context import GitCodeRepositorySourceContext
@@ -45,6 +46,17 @@ def test_checkouts_share_the_laptop_runtime(scope, tmp_path):
     assert other.catalog_path == first.catalog_path == tmp_path / 'stores' / 'metatables.sqlite'
+def test_existing_laptop_runtime_keeps_its_marker_identity(scope, tmp_path):
+    source, values = scope
+    moved = uuid4()
+    marker = tmp_path / 'stores' / 'metatables.sqlite.metatables-scope.json'
+    marker.parent.mkdir(parents=True)
+    marker.write_text(json.dumps({'workspace_uid': str(moved), 'purpose': 'runtime'}))
+    workspace = select_local_workspace(source=replace(source, repository_root=tmp_path / 'new-project'), values=values)
+    assert workspace.uid == moved
+    assert workspace.data_source.uid == uuid5(moved, 'tables')
 @pytest.mark.parametrize('setting,value', [
     ('METATABLES_CATALOG_DATABASE_URL','postgresql://remote/production'),
     ('METATABLES_CATALOG_DATABASE_URL','sqlite:///:memory:'),

@@ -632,7 +632,7 @@ server = [
 [[package]]
 name = "mainsequence-metatable"
-version = "0.1.10"
+version = "0.1.11"
 source = { editable = "." }
 dependencies = [
     { name = "alembic" },

mainsequence-metatable 0.1.10.dev21__tar.gz → 0.1.11.dev22__tar.gz

mainsequence-metatable 0.1.10.dev21tar.gz → 0.1.11.dev22tar.gz