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.
What does it do?
Added information about the schema when executing a request for clear inverse order column
Why is it needed?
Merging this PR will solve the entity duplication error when using a potgresql database when using a non-default schema.
How to test it?
For testing, you need to use a postgresql database (declared in docker-compose.dev.yml is sufficient). You need to run the getstarted application on NOT THE DEFAULT SCHEMA postgresql (If the schema is default for postgresql, then the query without specifying the schema will succeed and the problem will not appear). After launch, you need to create 2 collection type entities:
Next, you need to create several products (product1 and product2). Then go to products by region and create a product: product from New York with a link to product1. After saving this product, you must return to the page for storing products by region and click the “Duplicate” button.
Also, when you enable logging of database queries, you can see a corrected database query of the following type (the query includes a schema):
Related issue(s)/PR(s)
Fix #20509