script for migrating old rem_status_log

[matthewberryman]

Can we just use existing local_areas in current master? Or otherwise need to write a script to add attributes column and make sure other triggers, functions and columns based on that are recreated.

[tomasholderness]

Hi @matthewberryman I've added a script: https://github.com/urbanriskmap/cognicity-schema/blob/master/build/upgrade_petabencana_local_areas.sql

If you run this on an old database prior to running upgrade.sh it'll make sure that existing local areas data follows the newer format. Doing it this way is a little safer just in case the order of local areas data changes at time of creation (local_areas.pkey is bigserial so generated at creation, and referenced in a number of places).

[matthewberryman]

@talltom the trouble is, due to the time delay thus far, we have new REM and reports data in the current database, and really need some way of (as title suggests) getting the old migrating old rem (and reports?) data across against the local areas in the new database (copies sent a while back via secure means but I can send again). Is there anyway of doing this or is the "best" path simply to wear losses of new data? :/