fix: handle ON CONFLICT for non-auto-generated primary keys in PL/pgSQL mode#16
Merged
fix: handle ON CONFLICT for non-auto-generated primary keys in PL/pgSQL mode#16
Conversation
…QL mode When using PL/pgSQL mode with string or manually-set primary keys, the generated INSERT statements now properly include ON CONFLICT clauses for idempotency. This prioritizes non-auto-generated PKs (string, UUID, manual integer IDs) over unique constraints, ensuring the SQL can be safely re-executed without failure. Includes comprehensive test coverage for string PKs, composite PKs, and mixed scenarios. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
edraobdu
force-pushed
the
fix/on-conflict
branch
from
0f61635 to
b148771
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using PL/pgSQL mode with string or manually-set primary keys, the generated INSERT statements now properly include ON CONFLICT clauses for idempotency. This prioritizes non-auto-generated PKs (string, UUID, manual integer IDs) over unique constraints, ensuring the SQL can be safely re-executed without failure. Includes comprehensive test coverage for string PKs, composite PKs, and mixed scenarios.
🤖 Generated with Claude Code