Re: [opennms-devel] Database backwards-compatibility change in OpenNMS 17

2015-05-22 Thread Seth Leger
FYI, this branch was just merged into develop for inclusion in 17. -- Seth On 5/21/15 8:16 AM, Seth Leger wrote: > Hi everyone, > > I wanted to give everyone a heads-up that there will be a Liquibase > migration in OpenNMS 17 that will remove some columns and triggers from > the database in the

Re: [opennms-devel] Database backwards-compatibility change in OpenNMS 17

2015-05-21 Thread Seth Leger
Hi Dustin, Just write a migration for the Linkd table removals. Yeah, rollbacks aren't necessary for that. There was no logical way to write rollbacks for the column removals either. -- Seth On 5/21/15 8:44 AM, Dustin Frisch wrote: > Is there anything to do for us if we are going to remove the

Re: [opennms-devel] Database backwards-compatibility change in OpenNMS 17

2015-05-21 Thread Dustin Frisch
Is there anything to do for us if we are going to remove the linkd tables? We do not have to build rollback statements for removing tables as we are loosing rollback capability anyways, right? Seth Leger wrote: > Hi everyone, > > I wanted to give everyone a heads-up that there will be a Liqui

[opennms-devel] Database backwards-compatibility change in OpenNMS 17

2015-05-21 Thread Seth Leger
Hi everyone, I wanted to give everyone a heads-up that there will be a Liquibase migration in OpenNMS 17 that will remove some columns and triggers from the database in the ipInterface, ifServices, and outages tables. These columns and triggers were in place to preserve backwards compatibility wi