Delete duplicate AssetBed records of "HL7MONITOR" asset_class
#1595
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
rithviknishad
requested review from
Ashesh3,
vigneshhari,
sainak and
khavinshankar
sainak
approved these changes
Sep 11, 2023
Ashesh3
approved these changes
Sep 11, 2023
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.
Proposed Changes
AssetBedrecords of asset_class: "HL7MONITOR" grouped by duplicate (asset_id,bed_id).Associated Issue
PatientAssetBedview #1325 but a migration to clean-up existing records was not made.Migrations tested with staging db clone
Before Migration
Query Asset Bed table with
asset_class=HL7MONITOR, asset_id=71 and bed_id=16(duplicates)After Migration
Query Asset Bed table with
asset_class=HL7MONITOR, asset_id=71 and bed_id=16Merge Checklist
/docs@coronasafe/care-backend-maintainers @coronasafe/care-backend-admins