The ones that are marked as "dbms==mysql" are ones that were moved to the setup file I think. The logic here was:
1) The current initialization xml file and liquibase update file can only be run on mysql 2) Fix the initialization xml files to work on any database 3) Update the initialization files so that new users are directly installing a 1.9 db (instead of it technically installing 1.5 and upgrading it to 1.9) 4) Mark the update-to-latest file changesets as mysql-only because only users that are upgrading will need to call them. And existing users will only be running mysql (see point 1) So if the the changeset was integrated with the initialization file it was marked as dbms=mysql. I don't know of a wiki page that he's edited, but this page is probably where things should go: https://wiki.openmrs.org/display/docs/Database+Update+Conventions Ben On Fri, Oct 7, 2011 at 10:09 PM, Darius Jazayeri <[email protected]>wrote: > Hi Saptarshi, > > I see that many liquibase changesets have dbms="mysql", including some that > haven't been released yet and I'd like to modify. > E.g. 20110425-1700-create-visit-attribute-table. What's up with those? > > Also, have you written a wiki page somewhere describing what steps we need > to take with our future changesets so that they work on all databases? > > -Darius > ------------------------------ > 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]
