Amp-Thread-ID: https://ampcode.com/threads/T-019bfe38-44f9-74fc-b369-9b0ab4ee93e8
Co-authored-by: Amp <[email protected]>

…from oban)

- Add catch-all expr clause for IN with non-list right side
- Extract list values from Ecto.Query.Tagged structs before generating IN clause
- Fall back to JSON_EACH for pre-encoded JSON arrays
- Fixes issue #63: Oban job state queries using ~w() sigil now work correctly

Amp-Thread-ID: https://ampcode.com/threads/T-019bfe38-44f9-74fc-b369-9b0ab4ee93e8
Co-authored-by: Amp <[email protected]>

Amp-Thread-ID: https://ampcode.com/threads/T-019bfe38-44f9-74fc-b369-9b0ab4ee93e8
Co-authored-by: Amp <[email protected]>

Datatype fixes for lists in IN clauses

The catch-all IN clause handler was wrapping SubQuery expressions in
JSON_EACH(), producing invalid SQL like:
  WHERE id IN (SELECT value FROM JSON_EACH(?))

This adds a specific pattern match for %Ecto.SubQuery{} before the
catch-all, generating proper inline subqueries:
  WHERE id IN (SELECT s0.id FROM table AS s0 WHERE ...)

Also adds a general SubQuery expression handler that properly resolves
parent query aliases and combination queries.

This fixes compatibility with libraries like Oban that use subqueries
in UPDATE...WHERE id IN (subquery) patterns.

Ecto's query planner transforms {:type, _, [expr, type]} AST nodes
into %Ecto.Query.Tagged{} structs. The SQL generator only handled
the pre-planning tuple form, causing type-wrapped fragments (e.g.
type(fragment(...), :integer)) to fall through to the catch-all
expr clause which rendered a single '?' placeholder. This caused
parameter count mismatches with Hrana/Turso.

Fixes Oban Web JobQuery.limit_query crash on completed jobs page.

fix: handle Ecto.SubQuery in IN expressions

Fix/tagged struct expr handling

…67

Adds in_expression_comprehensive_test.exs to catch regressions in:

1. Issue #63: JSON encoding of list parameters in IN clauses
   - Simple list parameters should expand to individual placeholders
   - ~w() sigils should be handled via %Ecto.Query.Tagged{} detection

2. PR #66: Subqueries in IN expressions (Oban pattern)
   - WHERE id IN (SELECT ...) should generate proper SQL subquery
   - Before fix: incorrectly wrapped in JSON_EACH() causing malformed JSON error
   - After fix: generates inline subquery with correct aliases

3. PR #67: Tagged struct and type-wrapped expressions
   - Post-planning %Ecto.Query.Tagged{} nodes must be handled
   - Type-wrapped fragments should not fall through to catch-all '?' placeholder
   - Before fix: parameter count mismatch with Hrana/Turso
   - After fix: correct parameter count and proper type handling

Tests include:
- Basic list parameter expansion
- Empty lists and single-element lists
- ~w() sigil handling (Oban Lite pattern)
- Multiple IN clauses combined
- Subqueries with WHERE, SELECT, complex filters
- Type-cast expressions
- Integration tests combining multiple patterns

All 15 tests pass with the fixes in place.

Relates to: #63, PR #65, PR #66, PR #67