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

bridge tables: be more conservative over data wrangling #104

Closed
peterdutey opened this issue Oct 11, 2022 · 0 comments
Closed

bridge tables: be more conservative over data wrangling #104

peterdutey opened this issue Oct 11, 2022 · 0 comments
Assignees
Milestone

Comments

@peterdutey
Copy link
Collaborator

Bridge table functions should be improved to only work on a predictable set of fields.
See for instance here

In a particular instance where encounter_id was included in the drug_prescriptions table, the left join with inpatient_episodes would create fields encounter_id.x and encounter_id.y and break the execution.
This would have been avoided had tblz_prescriptions been built with a conservative select() statement.

@peterdutey peterdutey added this to the v0.5.3 milestone Oct 11, 2022
@peterdutey peterdutey self-assigned this Oct 11, 2022
peterdutey added a commit that referenced this issue Oct 23, 2022
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

No branches or pull requests

1 participant