Table differences between migrated and non-migrated databases
From IMSMA Wiki
Depending on if a database is originally created with 5.x or 6.0 there are also differences in Foreign keys' CASCADE on delete. |
If a database has been migrated from Legacy (at least from 2010) then some columns have been changed.
Table | Column | Initial 6.0 DB | Migrated DB |
hazard & hazardinfoversion | medicalfacilitylevel1 | varchar(50) | text |
hazard & hazardinfoversion | medicalfacilitylevel2 | varchar(50) | text |
hazreduc & hazreducinfoversion | medicalfacilitylevel1 | varchar(50) | text |
hazreduc & hazreducinfoversion | medicalfacilitylevel2 | varchar(50) | text |
hazreduc & hazreducinfoversion | teamid | varchar(38) | varchar(50) |
hazreduc & hazreducinfoversion | teamlocation | varchar(50) | text |
translation | translation | varchar(250 ) | text |
I can see in the migration scripts that previously also the following columns were different.
Table | Column |
fieldreport | reportedby |
geopoint | pointdescription |
hazreduc & hazreducinfoversion | qacomments |
hazreduc & hazreducinfoversion | vistor |
impactsurvey & impactsurveyversion | minehistorycomments |