sync ilios2 and ilios3 - third iteration.

[stopfstedt]

follows #990

the migrated default ilios2 schema does not align with a a freshly installed default ilios3 schema.

see https://gist.github.com/stopfstedt/8bceafcab3f997bd8686

eliminate any outstanding deviations.

[jrjohnson]

Well I'm down to the ordering of CONSTRAINTs and I have no idea how to resolve it.

vagrant@ilios:~$ mysqldbcompare  --run-all-tests --skip-data-check --skip-row-count --skip-table-options ilios_default:ilios_fresh

# Object definitions differ. (--changes-for=server1)
#

--- `ilios_default`.`session_learning_material`
+++ `ilios_fresh`.`session_learning_material`
@@ -9,6 +9,6 @@
   KEY `session_lm_k` (`session_id`,`learning_material_id`),
   KEY `learning_material_id_k` (`learning_material_id`),
   KEY `IDX_9BE2AF8D613FECDF` (`session_id`),
-  CONSTRAINT `FK_9BE2AF8D613FECDF` FOREIGN KEY (`session_id`) REFERENCES `session` (`session_id`),
-  CONSTRAINT `FK_9BE2AF8DC1D99609` FOREIGN KEY (`learning_material_id`) REFERENCES `learning_material` (`learning_material_id`)
+  CONSTRAINT `FK_9BE2AF8DC1D99609` FOREIGN KEY (`learning_material_id`) REFERENCES `learning_material` (`learning_material_id`),
+  CONSTRAINT `FK_9BE2AF8D613FECDF` FOREIGN KEY (`session_id`) REFERENCES `session` (`session_id`)
 )

These are identical foreign keys and they are both of the FK_FOO type which is what doctrine creates. So there should be no way for them to exist prior to this update. Why would an empty version of the ilios2 migration 31 database be different in this way from ucsf demo database?

Any thoughts?