Thursday, June 03, 2004
New Constraints in Release 3
I was asked to prepare a list of constraints which have been added in Release 3. Here they all are, MINUS constraints on brand new tables (like Information Routes).
1. ALL tables now have a Unique Key (UK) constraint which prevents simultaneous colliding transactions. If any provincial implementation database has suffered such a transaction, and this has not been repaired, then data conversion into the PRS3 database will fail for that table (reporting a Unique Key violation). This will have to be addressed at conversion time.
2. The Release 2.05 DSP and CPG tables are now merged. Thus, although there used to be a UK constraint on each of the DSP ID and the CPG ID, there is, in effect, a new UK constraint on the merged set of DSP IDs and CPG IDs. (APG IDs).
3. In GRS_BATCH_FILE_INPUT and GRS_BATCH_FILE_OUTPUT, FILEPATH_TXT and REGISTRY_USER_ORG_CHID are now mandatory. They should never have been optional, but it might have been possible for a DBA in a provincial installation to nullify these columns. It is mandatory in the application.
4. In GRS_ORG_NAMES, ORGNZTN_NAME_TXT is now mandatory. It is mandatory in the application.
5. In GRS_PERSON_NAMES, PRSN_FIRST_GIVEN_NAME_TXT and PRSN_SURNAME_TXT are now mandatory. It is mandatory in the application.
6. In GRS_TELEPHONES, TELECOMMUNICATION_NMBR_NUM is now mandatory. It is mandatory in the application.
7. In PRS_DEMOGRAPHIC_DETAILS, DATE_OF_BIRTH_DATE and GENDER_CODE are now mandatory. It is mandatory in the application.
8. In PRS_CONFIDENTIALITY_INDICATORS, CONFIDENTIAL_FLAG is now mandatory. It is mandatory in the application.
9. In PRS_PROVIDERS, PARTY_TYPE_CODE (IND/ORG) is now mandatory. It is mandatory in the application.
10. In PRS_PROVIDER_SUB_ROLES, PROVIDER_SUB_ROLE_TYPE_CODE is now mandatory. It is mandatory in the application.
1. ALL tables now have a Unique Key (UK) constraint which prevents simultaneous colliding transactions. If any provincial implementation database has suffered such a transaction, and this has not been repaired, then data conversion into the PRS3 database will fail for that table (reporting a Unique Key violation). This will have to be addressed at conversion time.
2. The Release 2.05 DSP and CPG tables are now merged. Thus, although there used to be a UK constraint on each of the DSP ID and the CPG ID, there is, in effect, a new UK constraint on the merged set of DSP IDs and CPG IDs. (APG IDs).
3. In GRS_BATCH_FILE_INPUT and GRS_BATCH_FILE_OUTPUT, FILEPATH_TXT and REGISTRY_USER_ORG_CHID are now mandatory. They should never have been optional, but it might have been possible for a DBA in a provincial installation to nullify these columns. It is mandatory in the application.
4. In GRS_ORG_NAMES, ORGNZTN_NAME_TXT is now mandatory. It is mandatory in the application.
5. In GRS_PERSON_NAMES, PRSN_FIRST_GIVEN_NAME_TXT and PRSN_SURNAME_TXT are now mandatory. It is mandatory in the application.
6. In GRS_TELEPHONES, TELECOMMUNICATION_NMBR_NUM is now mandatory. It is mandatory in the application.
7. In PRS_DEMOGRAPHIC_DETAILS, DATE_OF_BIRTH_DATE and GENDER_CODE are now mandatory. It is mandatory in the application.
8. In PRS_CONFIDENTIALITY_INDICATORS, CONFIDENTIAL_FLAG is now mandatory. It is mandatory in the application.
9. In PRS_PROVIDERS, PARTY_TYPE_CODE (IND/ORG) is now mandatory. It is mandatory in the application.
10. In PRS_PROVIDER_SUB_ROLES, PROVIDER_SUB_ROLE_TYPE_CODE is now mandatory. It is mandatory in the application.
