Create model for purposes_uses table
#335
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
https://eaflood.atlassian.net/browse/WATER-4046 Whilst working on ticket 4046 we have realised that we need a model for the `purpose_uses` table to be able to match the Returns to a charge purpose. The Return has a value in the `metadata` that matches to the `legacy_id` in the `purpose_uses` table.
Jozzey
changed the title
purpose_uses tablepurposes_uses table
StuAA78
approved these changes
Aug 4, 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.
https://eaflood.atlassian.net/browse/WATER-4046
Whilst working on ticket 4046 we have realised that we need a model for the
purposes_usestable to be able to match the Returns to a charge purpose. The Return has a value in themetadatathat matches to thelegacy_idin thepurposes_usestable.I also noticed while working on this model that we hadn't used the correct naming conventions for the file names of the
returnsschema migrations that we had recently built. Also in the migration20230802134153_create-returns-returnsthe constraints & defaults had been omitted so I also added these.