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

[DOCS]: Investigate and generate the full migration of the Silva/Results #606

Open
paulushcgcj opened this issue Feb 7, 2025 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@paulushcgcj
Copy link
Contributor

Documentation Topic

Update our limited migration to include the entire silva scope

Description

To increase our knowledge of the results application and what applications and information are part of our application or depend on it, we need the full table schema. This will allow us to understand some business rules and how results interact with other domains and applications.

With this information in hand, we will be able to generate the complete migration of our application database to reproduce it on a limited environment, where we will be able to properly explore the data connections while we recreate some of the existing scenarios in preparation for a future modernization, where we could migrate the data out of the existing database, while modernizing it.

Related Files or URLs

https://github.com/bcgov/nr-silva/blob/main/backend/src/test/resources/migration/oracle/V001__oracle_init.sql

Additional Notes

Above is the migration we're using right now, which only includes a subset of the tables we need. Ideally, we would expect a couple of migrations, being one for the core data, which are the tables that are the center of the application, another one for the peripheric tables, which are tables that relates to the core ones but doesn't contain essential data, and the last one would be a dependency migration, with a couple of tables that we relate to (through foreign keys) that are not part of our application domain, but we need in order to maintain data integrity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Status: New
Development

No branches or pull requests

2 participants