-
Notifications
You must be signed in to change notification settings - Fork 1
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
Establish KRR DB schema #186
Comments
The database script:
|
We follow the database-first approach. However, if we decide to go with a code-first approach, I can create the data models, configure the DbContext, write migrations, and use an in-memory database for testing. |
I want a shorter schema name. I was thinking about simply "krr". |
We can rename |
I've commented on most of the ideas you have @Ahmed-Ghanam |
Til info @SandGrainOne:
|
We will use your schema name suggestion:
The |
I think we can go forward with these names as they are for now. |
Description
Current plan is to copy the schema/structure from Altinn2. Use Entity Framework to import the schemas defined in Altinn 2. Posibly only 3 tables.
There should also be a column for user preferred language. I believe it's a new value Altinn 2 never added support for.
Acceptance criteria:
Recommendations for improvement
org_number_ak, latest_change_number, exported
andreservation
. It is not immediately apparent what their purpose is at first glance.mailbox_supplier
table will guarantee that each supplier has a distinct identifier.exported
column in thecontact_and_reservation.metadata
table, we can set a default value of the current timestamp to streamline data entry.contact_and_reservation.register.email_address
field to 255 characters to optimize storage.mobile_phone_number_last_updated
andemail_address_last_updated
fields are consistently updated, implementing a trigger to automatically set these values upon record changes would reduce the chance of manual errors.ON DELETE CASCADE
action for themailbox_supplier_id_fk
foreign key in thecontact_and_reservation.register
table, will help maintain referential integrity.The text was updated successfully, but these errors were encountered: