Sunny, thanks! So, rolling these changes back to previous versions of OpenMRS, what is the best practice? For 1.9.x, 1.8.x and 1.7.x (I assume 1.6.x is not necessary anymore).
Jeremy Keiper OpenMRS Core Developer AMPATH / IU-Kenya Support On Fri, Mar 30, 2012 at 10:31 AM, Saptarshi Purkayastha <[email protected]>wrote: > Hi Jeremy, > > ext:modifyColumn is necessary after we have upgraded to liquibase 2.0, > because it was removed from liquibase and made into an extension that we > have modified slightly > Some details are here: https://wiki.openmrs.org/display/docs/1.8+to+1.9 > > Also, it best to avoid the ext:modifyColumn tag in liquibase. Instead > modifyDatatype<http://www.liquibase.org/manual/modify_datatype_refactoring>or > similar one from here: > http://www.liquibase.org/manual/refactoring_commands > > --- > Regards, > Saptarshi PURKAYASTHA > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE > > > > On 30 March 2012 19:54, Jeremy Keiper <[email protected]> wrote: > >> Saptarshi, or anyone else who would know this: >> >> If I want to add a modifyColumn command to trunk's liquibase xml, should >> I use <ext:modifyColumn>? I noticed that all modifyColumn entries use that >> format. Is it preferred / necessary? >> >> Jeremy Keiper >> OpenMRS Core Developer >> AMPATH / IU-Kenya Support >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
