Critically looking into this issue, I pecked through the reporting module version 0.7.6 which is currently running on our platform 1.9.2(which was upgraded to 1.11.5) and found out the following:
-
The constraint in question was introduced here
-
Later, the column datatypes were modified and changed here to point to the uuids(That is what we still have in the upgraded version from 1.9.2 to 1.11.5)
-
Then it was dropped on the subsequent line. Looks like our database never hit this line and therefore retaining what is in the second bullet.
Questions: and maybe get it from @mseaton and @wyclif, is there any potential data loss, disconnections and system malfunctions if that constraint is removed per the flow of events? What was its intended for in the first place? and why is it NOT available in subsequent versions? was that redundant?
cc @dkayiwa