narrow-upsert-to-update

What problem does it solve?

It removes wasteful “read full row → rebind most fields → overwrite a few → call shared merge” behavior by splitting exactly one legacy ActionSet upsert path into a dedicated, narrow SQL XML update.

Core Features & Use Cases

• Single-path refactor with hard scope limits: targets exactly one user-specified actionId(queryId) and keeps the shared m_*_merge query unchanged.
• Proves changed fields before editing: traces where each value is loaded, transformed, overwritten, or preserved so the new SET contains only proven changed columns.
• Correct timestamp/audit handling: preserves NOW()-based semantics or upgrades to an application-generated current time parameter when appropriate, adding change-time when identifiable.
• Maintains migration traceability: adds required source-preservation comments carrying the original C# BO file and line range at both the Java call site and the new SQL XML query.

Quick Start

Use the skill to inspect one specific actionId(queryId) save path, validate test coverage first, then generate a minimal diff that adds exactly one dedicated update query and swaps only that one call site.