Fix duplicate alias generation when joining same relationship multiple times #214
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.
Summary
generateAliasForRelationship()where usingtime()for alias generation caused duplicate aliases when called multiple times within the same secondtime()withuniqid('', true)to ensure truly unique aliases are generated consistentlyTechnical Details
Problem
The
generateAliasForRelationshipmethod inJoinsHelper.phpwas usingtime()to generate unique aliases:Since most code executions complete within the same second, multiple calls to this method would produce identical aliases, causing later joins to overwrite earlier ones. This resulted in:
Solution
Replaced
time()withuniqid('', true)which:Changes Made
Core Fix: Updated
src/JoinsHelper.phplines 157-158 and 162md5($relationName.'table1'.time())→md5($relationName.'table1'.uniqid('', true))md5($relationName.'table2'.time())→md5($relationName.'table2'.uniqid('', true))md5($relationName.time())→md5($relationName.uniqid('', true))Test Coverage: Added
tests/DuplicateAliasGenerationTest.phpwith tests for:Test plan
🤖 Generated with opencode