New query design for PostgreSQL repository #8524
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Mandy Chessell <mandy.e.chessell@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR changes the SQL queries for the PostgreSQL repository to using nested selects (subqueries) that than joins between the header table and attribute value table. This is to allow nested property queries.
Related Issue(s)
The URL for complext searchies in Metadata Explorer OMVS have changed from
.../by_search_specificationto.../by-search-conditions. This is so we can reserve the phrase "search specification" for a multi-element search.Testing
Manual testing of each of the metdata explorer calls.
Release Notes & Documentation
Internal changes
Additional notes
None