185

[RAprogramm]

Closes #185.

The generated upsert existed only on the pool-backed repository; login-style flows that must share a transaction with adjacent statements (release a stale unique value, then upsert) were forced back to hand-written INSERT ... ON CONFLICT.

Behavior

• With both transactions and upsert(...), {Entity}TransactionRepo gains upsert with identical SQL and action semantics (update → Entity, nothing → Option<Entity>), executed on the transaction handle
• Absent without either attribute; create-fields requirement matches the pool method

Testing

• 3 adapter codegen tests (update/nothing shapes, gating) — 671+3 green under postgres,transactions
• trybuild upsert pass case extended: adapter upsert exercised inside begin()/commit()
• clippy -D warnings clean, all-features suite green, deny ok — checklist run before commit

Docs

• README upsert section notes the transactional variant; wiki (Attributes ×5) updated in this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!