You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: