Add hash generation to migration file

Issue #288 resolved
Ed McDonagh created an issue

Current migration file for upgrades doesn't know about the hash versions of each variable in the unique names table

Comments (5)

  1. Ed McDonagh reporter

    Added hash related code to the upgrade migration file. @dplatten - am I allowed to simply import remapp functions like this? Does this look like it would work? Refs#288

    → <<cset e99ae333ae8a>>

  2. Ed McDonagh reporter

    Added @dplatten's populate_study_workload_chart_time and populate_unique_equipment_names functions to the automatically generated migration from a 0.6 database to a 0.7 database. Ignored PostgreSQL median for now. Refs #288, #290

    → <<cset ddfeab318c5c>>

  3. Ed McDonagh reporter

    This has been tested in the latest migration file that deals with all the new tables, and it works.

  4. Log in to comment