Changes

Upgrade from 5.08.04 to 6.0 process

108 bytes added, 12:14, 21 September 2015
no edit summary
The dump file created with the tool is a '''raw''' dump file in PosGreSQL format which is possible to restore with V6.0.
''Raw'' as in it is PostgreSQL format but the table structure, etc. are still 5.08.04 and needs to be upgraded to V6.0.
<li> The upgrade scripts do not handle the '''subobjects ''' that should be transformed into normal multi-selects well (2014-11-25/NAA).Run these '''[[Check Detection Sample Sector VegetationRemoval | queries]]''' in order to see if there are any records in these tables that later will have to be inserted manually '''(mandatory)'''in other tables in PostgreSQL. If there are rows you need to '''export''' them and '''manually''' add them the values in the correct tables with SQL after the upgrade.</li>
</ol>
===Restore the raw dump (mandatory)===__NOEDITSECTION__
#: Duplicate enumvalues cause import issues i.e. empty fields, which are difficult to detect due to there are no error messages;
# Check if the upgrade scripts '''wrongly''' changed enumvalues to Inactive ('''mandatory''')('''[[Inactive enumvalue fix | query ]]''')(still happening with 18 Feb 2015);
# If needed '''add''' Detection/Samle/Sector/Vegetation removal records to the correct tablese.g. hazreducinfoversion_has_imsmaenum;
# The upgrade script should have changed all points that used Location point to Reference point but it does not. If there are any Location points you need to inform the country that the type has changed to Reference points. These [[Location point| queries]] will do the update.
6,632
edits