Cloned object make different SQL from the original. #51
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.
About SQL::Maker::select_query,
If it has scalar reference in select, SQL from cloned object is not same SQL with the one from an original object.
It causes that scalar reference's address is used as key of
select_map
.So, in this fix, creating select_map from select_map_reverse in
as_sql
.And if single scalar reference is given as
$term
in select, dereference it and set it to $col before$col ||= $term
.