COmanage Developers List

[Benn Oshrin <>]

On 12/27/14 3:54 PM, Scott Koranda (JIRA) wrote:
> Specific issues include:
> 1) The name 'co_extended_types_i2' for an index is used more than once 
> (probably a cut and paste error).

I'm not sure that adodb will catch this and rename an index on a schema 
update. You may need to write migration documentation. See already 
existing similar notes at

https://spaces.internet2.edu/display/COmanage/Upgrading+Registry+to+v0.9.2#UpgradingRegistrytov0.9.2-FixIncorrectForeignKey

> 2) The table 'email_addresses' appears too late in the schema, preventing the 
> table co_invites from properly referencing it.

I don't see this foreign key missing in my (recent) databases, though 
that could be because adodb picks it up on a subsequent run (eg: during 
an upgrade).

> 3) The name 'co_settings_i1' for an index is used more than once (probably a 
> cut and paste error).

Same comment as #1.

> 4) The table co_provisioning_queued_events references co_provisioning_targets but 
> does not properly include the 'cm_' prefix inside of the <constraint> element.

I don't think anything uses this table so the impact from this should be 
pretty minimal.

Thanks,

-Benn-