ocean · ocean · Jan 2, 2026 · Dec 30, 2025 · Dec 31, 2025 · Dec 31, 2025
diff --git a/.beads/.gitignore b/.beads/.gitignore
@@ -27,8 +27,8 @@ beads.left.meta.json
 beads.right.jsonl
 beads.right.meta.json
 
-# Keep JSONL exports and config (source of truth for git)
-!issues.jsonl
-!interactions.jsonl
-!metadata.json
-!config.json
+# NOTE: Do NOT add negation patterns (e.g., !issues.jsonl) here.
+# They would override fork protection in .git/info/exclude, allowing
+# contributors to accidentally commit upstream issue databases.
+# The JSONL files (issues.jsonl, interactions.jsonl) and config files
+# are tracked by git by default since no pattern above ignores them.
diff --git a/.beads/config.yaml b/.beads/config.yaml
@@ -6,7 +6,7 @@
 # Issue prefix for this repository (used by bd init)
 # If not set, bd init will auto-detect from directory name
 # Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
-# issue-prefix: ""
+issue-prefix: "el"
 
 # Use no-db mode: load from JSONL, no SQLite, write back after each command
 # When true, bd will use .beads/issues.jsonl as the source of truth

diff --git a/.beads/issues.jsonl b/.beads/issues.jsonl
diff --git a/.claude/settings.local.json b/.claude/settings.local.json
@@ -43,7 +43,12 @@
       "Bash(mix sobelow:*)",
       "Bash(git stash:*)",
       "Bash(git --no-pager log:*)",
-      "Bash(bd:*)"
+      "Bash(bd:*)",
+      "Bash(git checkout:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(git push)",
+      "Bash(git --no-pager status)"
     ],
     "deny": [],
     "ask": []

diff --git a/AGENTS.md b/AGENTS.md
@@ -485,7 +485,115 @@ end)
 
 ### Prepared Statements
 
-Prepared statements offer significant performance improvements for repeated queries and prevent SQL injection. As of v0.7.0, statement caching is automatic and highly optimised.
+Prepared statements offer significant performance improvements for repeated queries and prevent SQL injection. As of v0.7.0, statement caching is automatic and highly optimised. Named parameters provide flexible parameter binding with three SQLite syntaxes.
+
+#### Named Parameters
+
+SQLite supports three named parameter syntaxes for more readable and maintainable queries:
+
+```elixir
+# Syntax 1: Colon prefix (:name)
+"SELECT * FROM users WHERE email = :email AND status = :status"
+
+# Syntax 2: At-sign prefix (@name)
+"SELECT * FROM users WHERE email = @email AND status = @status"
+
+# Syntax 3: Dollar sign prefix ($name)
+"SELECT * FROM users WHERE email = $email AND status = $status"
+```
+
+Execute with map-based parameters:
+
+```elixir
+# Prepared statement with named parameters
+{:ok, stmt_id} = EctoLibSql.Native.prepare(
+  state,
+  "SELECT * FROM users WHERE email = :email AND status = :status"
+)
+
+{:ok, result} = EctoLibSql.Native.query_stmt(
+  state,
+  stmt_id,
+  %{"email" => "[email protected]", "status" => "active"}
+)
+```
+
+Direct execution with named parameters:
+
+```elixir
+# INSERT with named parameters
+{:ok, _, _, state} = EctoLibSql.handle_execute(
+  "INSERT INTO users (name, email, age) VALUES (:name, :email, :age)",
+  %{"name" => "Alice", "email" => "[email protected]", "age" => 30},
+  [],
+  state
+)
+
+# UPDATE with named parameters
+{:ok, _, _, state} = EctoLibSql.handle_execute(
+  "UPDATE users SET status = :status, updated_at = :now WHERE id = :user_id",
+  %{"status" => "inactive", "now" => DateTime.utc_now(), "user_id" => 123},
+  [],
+  state
+)
+
+# DELETE with named parameters
+{:ok, _, _, state} = EctoLibSql.handle_execute(
+  "DELETE FROM users WHERE id = :user_id AND email = :email",
+  %{"user_id" => 123, "email" => "[email protected]"},
+  [],
+  state
+)
+```
+
+Named parameters in transactions:
+
+```elixir
+{:ok, :begin, state} = EctoLibSql.handle_begin([], state)
+
+{:ok, _, _, state} = EctoLibSql.handle_execute(
+  """
+  INSERT INTO users (name, email) VALUES (:name, :email)
+  """,
+  %{"name" => "Alice", "email" => "[email protected]"},
+  [],
+  state
+)
+
+{:ok, _, _, state} = EctoLibSql.handle_execute(
+  "UPDATE users SET verified = 1 WHERE email = :email",
+  %{"email" => "[email protected]"},
+  [],
+  state
+)
+
+{:ok, _, state} = EctoLibSql.handle_commit([], state)
+```
+
+**Benefits:**
+- **Readability**: Clear parameter names make queries self-documenting
+- **Maintainability**: Easier to refactor when parameter names are explicit
+- **Type safety**: Parameter validation can check required parameters upfront
+- **Flexibility**: Use any of three SQLite syntaxes interchangeably
+- **Prevention**: Prevents SQL injection attacks through proper parameter binding
+
+**Backward Compatibility:**
+Positional parameters (`?`) still work unchanged:
+
+```elixir
+# Positional parameters still work
+{:ok, _, result, state} = EctoLibSql.handle_execute(
+  "SELECT * FROM users WHERE email = ? AND status = ?",
+  ["[email protected]", "active"],
+  [],
+  state
+)
+
+# Named and positional can coexist in separate queries within the same codebase
+```
+
+**Avoiding Mixed Syntax:**
+While SQLite technically permits mixing positional (`?`) and named (`:name`) parameters in a single statement, this is discouraged. Named parameters receive implicit numeric indices which can conflict with positional parameters, leading to unexpected binding order. This adapter's map-based approach naturally avoids this issue—pass a list for positional queries, or a map for named queries, but don't mix within a single statement.
 
 #### How Statement Caching Works
 
@@ -1345,6 +1453,100 @@ mix ecto.migrate   # Run migrations
 mix ecto.rollback  # Rollback last migration
 ```
 
+#### STRICT Tables (Type Enforcement)
+
+STRICT tables enforce strict type checking - columns must be one of the allowed SQLite types. This prevents accidental type mismatches and data corruption:
+
+```elixir
+# Create a STRICT table for type safety
+defmodule MyApp.Repo.Migrations.CreateUsers do
+  use Ecto.Migration
+
+  def change do
+    create table(:users, strict: true) do
+      add :id, :integer, primary_key: true
+      add :name, :string, null: false
+      add :email, :string, null: false
+      add :age, :integer
+      add :balance, :float, default: 0.0
+      add :avatar, :binary
+      add :is_active, :boolean, default: true
+
+      timestamps()
+    end
+
+    create unique_index(:users, [:email])
+  end
+end
+```
+
+**Benefits:**
+- **Type Safety**: Enforces that columns only accept their declared types (TEXT, INTEGER, REAL, BLOB, NULL)
+- **Data Integrity**: Prevents accidental type coercion that could lead to bugs
+- **Better Errors**: Clear error messages when incorrect types are inserted
+- **Performance**: Can enable better query optimisation by knowing exact column types
+
+**Allowed Types in STRICT Tables:**
+- `INT`, `INTEGER` - Integer values only
+- `TEXT` - Text values only
+- `BLOB` - Binary data only
+- `REAL` - Floating-point values only
+- `NULL` - NULL values only (rarely used)
+
+**Usage Examples:**
+
+```elixir
+# STRICT table with various types
+create table(:products, strict: true) do
+  add :sku, :string, null: false              # Must be TEXT
+  add :name, :string, null: false             # Must be TEXT
+  add :quantity, :integer, default: 0         # Must be INTEGER
+  add :price, :float, null: false             # Must be REAL
+  add :description, :text                     # Must be TEXT
+  add :image_data, :binary                    # Must be BLOB
+  add :published_at, :utc_datetime            # Stored as TEXT (ISO8601 format)
+  timestamps()
+end
+
+# Combining STRICT with RANDOM ROWID
+create table(:api_keys, options: [strict: true, random_rowid: true]) do
+  add :user_id, references(:users, on_delete: :delete_all)  # INTEGER
+  add :key, :string, null: false                            # TEXT
+  add :secret, :string, null: false                         # TEXT
+  add :last_used_at, :utc_datetime                          # TEXT
+  timestamps()
+end
+```
+
+**Restrictions:**
+- STRICT is a libSQL/SQLite 3.37+ extension (not available in older versions)
+- Type affinity is enforced: generic types like `TEXT(50)` or `DATE` are not allowed
+- Dynamic type changes (e.g., storing integers in TEXT columns) will fail with type errors
+- Standard SQLite does not support STRICT tables
+
+**SQL Output:**
+```sql
+CREATE TABLE users (
+  id INTEGER PRIMARY KEY,
+  name TEXT NOT NULL,
+  email TEXT NOT NULL,
+  age INTEGER,
+  balance REAL DEFAULT 0.0,
+  avatar BLOB,
+  is_active INTEGER DEFAULT 1,
+  inserted_at TEXT,
+  updated_at TEXT
+) STRICT
+```
+
+**Error Example:**
+```elixir
+# This will fail on a STRICT table:
+Repo.query!("INSERT INTO users (name, email, age) VALUES (?, ?, ?)",
+  [123, "[email protected]", "thirty"])  # ← age is string, not INTEGER
+# Error: "Type mismatch" (SQLite enforces STRICT)
+```
+
 #### RANDOM ROWID Support (libSQL Extension)
 
 For security and privacy, use RANDOM ROWID to generate pseudorandom row IDs instead of sequential integers:

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -9,6 +9,56 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- **Named Parameters Execution Support**
+  - Full support for SQLite named parameter syntax in prepared statements and direct execution
+  - **Three SQLite syntaxes supported**: `:name`, `@name`, `$name`
+  - **Transparent conversion**: Map-based named parameters automatically converted to positional arguments for internal execution
+  - **Use cases**: Dynamic query building, parameter validation, better debuggability, API introspection
+  - **Execution paths**: Works with prepared statements, transactions, batch operations, and cursor streaming
+  - **Backward compatibility**: Existing positional parameter syntax (`?`) continues to work unchanged
+  - **Implementation**: Automatic parameter binding detection and conversion in both transactional and non-transactional paths
+  - **Usage examples**:
+    ```elixir
+    # Named parameters in prepared statements
+    {:ok, stmt_id} = EctoLibSql.Native.prepare(
+      state,
+      "SELECT * FROM users WHERE email = :email AND status = :status"
+    )
+
+    # Execute with named parameters as map
+    {:ok, result} = EctoLibSql.Native.query_stmt(
+      state,
+      stmt_id,
+      %{"email" => "[email protected]", "status" => "active"}
+    )
+
+    # Alternative syntaxes
+    "SELECT * FROM users WHERE email = @email"
+    "SELECT * FROM users WHERE email = $email"
+
+    # Works with direct execution
+    {:ok, _, result, state} = EctoLibSql.handle_execute(
+      "INSERT INTO users (name, email) VALUES (:name, :email)",
+      %{"name" => "Alice", "email" => "[email protected]"},
+      [],
+      state
+    )
+
+    # Works with transactions
+    {:ok, :begin, state} = EctoLibSql.handle_begin([], state)
+    {:ok, _, _, state} = EctoLibSql.handle_execute(
+      "UPDATE users SET status = :status WHERE id = :id",
+      %{"status" => "inactive", "id" => 123},
+      [],
+      state
+    )
+    {:ok, _, state} = EctoLibSql.handle_commit([], state)
+    ```
+  - **Type handling**: All value types (strings, integers, floats, binaries, nil) properly converted
+  - **Parameter validation**: Uses `stmt_parameter_name/3` introspection for validation
+  - **Edge cases handled**: Empty parameter maps, missing parameters with proper error messages, mixed positional and named parameters
+  - **Added comprehensive test coverage** in `test/named_parameters_execution_test.exs` covering all SQLite syntaxes, CRUD operations, transactions, batch operations, and backward compatibility
+
 - **Query-Based UPSERT Support (on_conflict with Ecto.Query)**
   - Extended `on_conflict` support to handle query-based updates
   - Allows using keyword list syntax for dynamic update operations:

diff --git a/lib/ecto/adapters/libsql/connection.ex b/lib/ecto/adapters/libsql/connection.ex
@@ -372,6 +372,19 @@ defmodule Ecto.Adapters.LibSql.Connection do
   end
 
   defp column_options(opts, composite_pk) do
+    # Validate generated column constraints (SQLite disallows these combinations).
+    if Keyword.has_key?(opts, :generated) do
+      if Keyword.has_key?(opts, :default) do
+        raise ArgumentError,
+              "generated columns cannot have a DEFAULT value (SQLite constraint)"
+      end
+
+      if Keyword.get(opts, :primary_key) do
+        raise ArgumentError,
+              "generated columns cannot be part of a PRIMARY KEY (SQLite constraint)"
+      end
+    end
+
     default = column_default(Keyword.get(opts, :default))
     null = if Keyword.get(opts, :null) == false, do: " NOT NULL", else: ""
 
@@ -381,7 +394,18 @@ defmodule Ecto.Adapters.LibSql.Connection do
         do: " PRIMARY KEY",
         else: ""
 
-    "#{pk}#{null}#{default}"
+    # Generated columns (SQLite 3.31+, libSQL 3.45.1+)
+    generated =
+      case Keyword.get(opts, :generated) do
+        nil ->
+          ""
+
+        expr when is_binary(expr) ->
+          stored = if Keyword.get(opts, :stored, false), do: " STORED", else: ""
+          " GENERATED ALWAYS AS (#{expr})#{stored}"
+      end
+
+    "#{pk}#{null}#{default}#{generated}"
   end
 
   defp column_default(nil), do: ""
@@ -429,13 +453,24 @@ defmodule Ecto.Adapters.LibSql.Connection do
       end
 
     # Table suffix options (go after closing parenthesis)
-    table_suffix =
+    suffixes = []
+
+    suffixes =
       if table.options && Keyword.get(table.options, :random_rowid, false) do
-        " RANDOM ROWID"
+        suffixes ++ [" RANDOM ROWID"]
       else
-        ""
+        suffixes
       end
 
+    suffixes =
+      if table.options && Keyword.get(table.options, :strict, false) do
+        suffixes ++ [" STRICT"]
+      else
+        suffixes
+      end
+
+    table_suffix = Enum.join(suffixes)
+
     {table_constraints, table_suffix}
   end