Fixing potentially ambiguous properties in get_orders() #2929
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.
All Submissions:
Changes proposed in this Pull Request:
When both
id
anddiscount_code_id
are used, theid
column in the database is ambiguous.This change defines the table for all search properties in get_orders().
Resolves XXX.
How to test the changes in this Pull Request:
Returns empty array before the fix, even if there is a matching order. After the fix, returns matching orders.
Other information:
Changelog entry