Fix duplicate function generation when indexes target same columns #423
+354
−7
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.
Fix duplicate function generation when indexes target same columns
Problem
When a table has multiple indexes targeting the same column(s), dbtpl generates duplicate function names, causing Go compilation errors.
Specific scenario: Tables with both primary keys and unique indexes on the same column generate identical function names:
Result: Two functions with identical signatures:
Error:
UserById redeclared in this blockSolution
This PR implements backwards-compatible duplicate detection and resolution:
_uniquefor conflicting unique indexes_idxfor conflicting regular indexesResults
Before (broken):
After (fixed):
Backwards Compatible:
Implementation
Test-Driven Development Approach:
Added failing test first (
TestIndexFuncNameDuplicates):TestBackwardsCompatibility)Implemented the fix:
indexFuncName()to generate base names without automatic suffixesassignUniqueIndexFuncNames()for conflict-aware name assignment with priority orderingVerified fix works:
Demo
Live demonstration available at: https://github.com/imran31415/dbdpl-demo-fix
Testing
Fixes #407