Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue #3390 - align ResourceTypeName with the R4 ResourceType enum #3561

Merged
merged 3 commits into from
Apr 5, 2022

Conversation

lmsurpre
Copy link
Member

@lmsurpre lmsurpre commented Apr 5, 2022

I could have sworn I did this before, but its definitely out-of-sync in
main. This changeset re-aligns the two so that:

  1. we don't end up trying to use a resource type that doesn't exit in R4
  2. we don't miss any resource types that existed in R4 but are being
    removed for R4B

Signed-off-by: Lee Surprenant [email protected]

I could have sworn I did this before, but its definitely out-of-sync in
main. This changeset re-aligns the two so that:
1. we don't end up trying to us a resource type that doesn't exit in R4
2. we don't miss any resource types that existed in R4 but are being
removed for R4B

Signed-off-by: Lee Surprenant <[email protected]>
We found that, due to the issue with ResourceTypeName, a system export
was invoking FHIRPersistenceJDBCImpl.changes() with a list of type names
that includes invalid values.

Previously, that led to an invalid SQL statement.  Now we will filter
out the invalid names (and throw if some were passed but none were
found).

Signed-off-by: Lee Surprenant <[email protected]>
…dbc/impl/FHIRPersistenceJDBCImpl.java


Signed-off-by: Lee Surprenant <[email protected]>

Co-authored-by: Robin Arnold <[email protected]>
Copy link
Collaborator

@punktilious punktilious left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lmsurpre lmsurpre merged commit a195cfc into main Apr 5, 2022
@lmsurpre lmsurpre deleted the issue-3390 branch April 5, 2022 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants