lambda-erp 0.1.3__tar.gz → 0.1.4__tar.gz

{lambda_erp-0.1.3 → lambda_erp-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: lambda-erp
-Version: 0.1.3
+Version: 0.1.4
 Summary: Core ERP logic - accounting, sales, purchasing, inventory
 Author: TORUS INVESTMENTS AG
 License-Expression: MIT
@@ -44,6 +44,13 @@ https://github.com/user-attachments/assets/1b2749ef-10e7-42f5-9cce-df5628292667
   <a href="https://discord.gg/ZwFh9hZJTb"><img alt="Join the Lambda ERP Discord" src="https://img.shields.io/discord/1496911123029557359?color=7289DA&label=Join%20on%20Discord&logo=discord&logoColor=white&style=for-the-badge"></a>
 </p>
 
+The two packages publish in lockstep on every release:
+
+<p>
+  <a href="https://pypi.org/project/lambda-erp/"><img alt="lambda-erp on PyPI" src="https://img.shields.io/pypi/v/lambda-erp?label=PyPI%20%7C%20lambda-erp&logo=pypi&logoColor=white"></a>
+  <a href="https://www.npmjs.com/package/@lambda-development/erp-core"><img alt="@lambda-development/erp-core on npm" src="https://img.shields.io/npm/v/@lambda-development/erp-core?label=npm%20%7C%20%40lambda-development%2Ferp-core&logo=npm"></a>
+</p>
+
 This release is not yet production-ready. It's a complete prototype but not vetted enough to run your payroll on it yet.
 
 ---

{lambda_erp-0.1.3 → lambda_erp-0.1.4}/README.md

@@ -20,6 +20,13 @@ https://github.com/user-attachments/assets/1b2749ef-10e7-42f5-9cce-df5628292667
   <a href="https://discord.gg/ZwFh9hZJTb"><img alt="Join the Lambda ERP Discord" src="https://img.shields.io/discord/1496911123029557359?color=7289DA&label=Join%20on%20Discord&logo=discord&logoColor=white&style=for-the-badge"></a>
 </p>
 
+The two packages publish in lockstep on every release:
+
+<p>
+  <a href="https://pypi.org/project/lambda-erp/"><img alt="lambda-erp on PyPI" src="https://img.shields.io/pypi/v/lambda-erp?label=PyPI%20%7C%20lambda-erp&logo=pypi&logoColor=white"></a>
+  <a href="https://www.npmjs.com/package/@lambda-development/erp-core"><img alt="@lambda-development/erp-core on npm" src="https://img.shields.io/npm/v/@lambda-development/erp-core?label=npm%20%7C%20%40lambda-development%2Ferp-core&logo=npm"></a>
+</p>
+
 This release is not yet production-ready. It's a complete prototype but not vetted enough to run your payroll on it yet.
 
 ---

{lambda_erp-0.1.3 → lambda_erp-0.1.4}/lambda_erp/database.py

@@ -9,12 +9,34 @@ Schema is created from Python table definitions instead of DocType JSON files.
 """
 
 import datetime as _datetime
+import os
 import sqlite3
 import threading
 from contextlib import contextmanager
 from lambda_erp.utils import _dict
 
 
+_VALID_JOURNAL_MODES = {"WAL", "DELETE", "TRUNCATE", "PERSIST", "MEMORY", "OFF"}
+
+
+def _journal_mode() -> str:
+    """SQLite journal mode for connections, from LAMBDA_ERP_SQLITE_JOURNAL_MODE.
+
+    Defaults to WAL — best for a local-disk DB (concurrent readers alongside a
+    writer). But WAL relies on a memory-mapped ``-shm`` file, so it does NOT work
+    on a network filesystem (SMB/NFS Azure Files, NFS mounts): the
+    ``PRAGMA journal_mode=WAL`` itself fails with "database is locked". A
+    deployment whose DB lives on such a share must set
+    ``LAMBDA_ERP_SQLITE_JOURNAL_MODE=DELETE`` — rollback-journal mode, which uses
+    only the byte-range locks the share does support. A single-writer deployment
+    (one replica, one worker) loses nothing by using DELETE. Unknown values fall
+    back to WAL. The value is validated against an allowlist before being
+    interpolated into the PRAGMA.
+    """
+    mode = os.environ.get("LAMBDA_ERP_SQLITE_JOURNAL_MODE", "WAL").strip().upper()
+    return mode if mode in _VALID_JOURNAL_MODES else "WAL"
+
+
 class _NullLock:
     """No-op context manager used when SQLite-level locking is sufficient."""
 
@@ -60,7 +82,7 @@ class Database:
         """
         conn = sqlite3.connect(self.db_path, check_same_thread=False)
         conn.row_factory = sqlite3.Row
-        conn.execute("PRAGMA journal_mode=WAL")
+        conn.execute(f"PRAGMA journal_mode={_journal_mode()}")
         conn.execute("PRAGMA foreign_keys=ON")
         # Wait up to 5s for the file lock instead of raising SQLITE_BUSY when
         # another thread is mid-write. Generous for our workload (LLM calls

{lambda_erp-0.1.3 → lambda_erp-0.1.4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "lambda-erp"
-version = "0.1.3"
+version = "0.1.4"
 description = "Core ERP logic - accounting, sales, purchasing, inventory"
 readme = "README.md"
 license = "MIT"