tina4-python 3.13.45__tar.gz → 3.13.46__tar.gz

{tina4_python-3.13.45 → tina4_python-3.13.46}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tina4-python
-Version: 3.13.45
+Version: 3.13.46
 Summary: Tina4 Python v3 — Zero-dependency, lightweight web framework
 Author-email: Andre van Zuydam <andrevanzuydam@gmail.com>
 License: MIT

{tina4_python-3.13.45 → tina4_python-3.13.46}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tina4-python"
-version = "3.13.45"
+version = "3.13.46"
 description = "Tina4 Python v3 — Zero-dependency, lightweight web framework"
 authors = [
     {name = "Andre van Zuydam", email = "andrevanzuydam@gmail.com"}

{tina4_python-3.13.45 → tina4_python-3.13.46}/tina4_python/__init__.py

@@ -8,7 +8,7 @@ Tina4 Python v3.0 — Zero-dependency, lightweight web framework.
 
 One import, everything works.
 """
-__version__ = "3.13.45"
+__version__ = "3.13.46"
 
 # ── Route decorators ──
 from tina4_python.core.router import (  # noqa: E402, F401

{tina4_python-3.13.45 → tina4_python-3.13.46}/tina4_python/database/sqlite.py

@@ -93,23 +93,43 @@ class SQLiteAdapter(DatabaseAdapter):
             )
 
     def execute_many(self, sql: str, params_list: list[list] = None) -> DatabaseResult:
-        """Optimized batch execute using SQLite's executemany."""
+        """Optimized batch execute using SQLite's executemany — ATOMIC (one txn).
+
+        The batch runs inside one transaction so a bad row mid-batch rolls the
+        WHOLE batch back (all-or-nothing) instead of leaving the rows applied
+        before the failure in an open, uncommitted transaction. Mirrors the base
+        DatabaseAdapter.execute_many owns-transaction guard and the other engines.
+        """
         sql = self._translate_sql(sql)
         rows = params_list or []
-        self._conn.executemany(sql, rows)
-
-        # cursor.rowcount / cursor.lastrowid are unreliable after executemany()
-        # in sqlite3 (rowcount can come back 0 or -1, lastrowid is not set) and
-        # were non-deterministic across pooled connections. The batch is
-        # all-or-raise, so every supplied row was applied; the last inserted id
-        # is read deterministically from last_insert_rowid() on this connection.
-        affected = len(rows)
-        last_row = self._conn.execute("SELECT last_insert_rowid()").fetchone()
-        last_id = last_row[0] if last_row and last_row[0] else None
-
-        if not self._in_transaction and self.autocommit:
-            if self._conn.in_transaction:
-                self._conn.execute("COMMIT")
+
+        # Own (and commit/rollback) the batch transaction only for a standalone
+        # write in autocommit mode — never inside a caller's explicit transaction.
+        standalone = self.autocommit and not self._in_transaction
+        if standalone and not self._conn.in_transaction:
+            self._conn.execute("BEGIN")
+
+        try:
+            self._conn.executemany(sql, rows)
+            # cursor.rowcount / cursor.lastrowid are unreliable after executemany()
+            # in sqlite3 (rowcount can come back 0 or -1, lastrowid is not set).
+            # The batch is all-or-nothing, so every supplied row was applied; read
+            # the last inserted id deterministically from last_insert_rowid().
+            affected = len(rows)
+            last_row = self._conn.execute("SELECT last_insert_rowid()").fetchone()
+            last_id = last_row[0] if last_row and last_row[0] else None
+        except Exception:
+            # Roll the partial batch back so nothing is left half-applied, then
+            # FAIL LOUD (re-raise) — parity with execute() and the other engines.
+            if standalone and self._conn.in_transaction:
+                try:
+                    self._conn.execute("ROLLBACK")
+                except Exception:
+                    pass
+            raise
+
+        if standalone and self._conn.in_transaction:
+            self._conn.execute("COMMIT")
 
         return DatabaseResult(
             affected_rows=affected,