Skip to content

BDMS-540: Link NMA_WeatherPhotos to NMA_WeatherData#470

Merged
jirhiker merged 2 commits intokas-bdms-540-NMA_SurfaceWaterPhotos-FK-relationshipfrom
kas-bdms-540-NMA_WeatherPhotos-FK-relationship
Feb 7, 2026
Merged

BDMS-540: Link NMA_WeatherPhotos to NMA_WeatherData#470
jirhiker merged 2 commits intokas-bdms-540-NMA_SurfaceWaterPhotos-FK-relationshipfrom
kas-bdms-540-NMA_WeatherPhotos-FK-relationship

Conversation

@ksmuczynski
Copy link
Copy Markdown
Contributor

@ksmuczynski ksmuczynski commented Feb 5, 2026

Why

This PR addresses the following problem / context:

  • NMA_WeatherPhotos lacked a direct FK relationship to WeatherData, making joins and integrity checks harder.

How

Implementation summary - the following was changed / added / removed:

  • Adds a WeatherID FK relationship between NMA_WeatherPhotos and NMA_WeatherData.
  • Updates the WeatherPhoto transfer to use the new relationship and aligns transfer helpers.
  • Extends legacy WeatherPhoto tests to cover the WeatherID relationship.
  • Adds the Alembic migration to create the FK and supporting uniqueness constraint.

Notes

Any special considerations, workarounds, or follow-up work to note?
- !! This is the last PR in the chain of "BDMS-540:..." PRs (467-469).

ksmuczynski and others added 2 commits February 5, 2026 16:40
…NMA_WeatherPhotos via WeatherID

- move weather_id under FK section and enforce NOT NULL
- add FK + relationship + validator on NMA_WeatherPhotos
- mark NMA_WeatherData.weather_id unique for FK target
- run WeatherPhotos transfer after WeatherData and skip orphan photos
- add migration to backfill/cleanup and enforce FK/NOT NULL
- update legacy tests to create WeatherPhotos with a real parent WeatherData
@jirhiker
Copy link
Copy Markdown
Member

jirhiker commented Feb 6, 2026

My hope was that these types of changes would be taken care of in the db refactor and data transformation step that is to follow the 1:1 migration. Given we are so close to having migrated all the data I'd like to limit the modifications to the transfer script

@ksmuczynski
Copy link
Copy Markdown
Contributor Author

Okay, I will revisit this on Monday.

@ksmuczynski
Copy link
Copy Markdown
Contributor Author

Do you suggest a rollback on all changes?

@jirhiker
Copy link
Copy Markdown
Member

jirhiker commented Feb 7, 2026

no, I think the only changes that potentially need to be rolled back are the changes to the transfer scripts. I think the outstanding question we all need to consider "is all the necessary data migrated from nma to ocotillo, for all models." The changes this PR makes seem like they could be accomplished without having to run a fresh transfer (?).

Basically, I want to move away from the "wholesale transfer model" and move into the "DB refactor and data transformation model" introduced in PR #464

As I write this tho I remember that another transfer is required to get some previously orphaned chemistry data migrated. so Im going to approve this

@jirhiker jirhiker merged commit 830609d into kas-bdms-540-NMA_SurfaceWaterPhotos-FK-relationship Feb 7, 2026
2 checks passed
@TylerAdamMartinez TylerAdamMartinez deleted the kas-bdms-540-NMA_WeatherPhotos-FK-relationship branch March 12, 2026 17:25
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