Thanks Andy that explains why UUIDs are wrong. We need a more formal way of upgrading the dictionary. Let's use JIRA for that. I've created https://tickets.openmrs.org/browse/STAND-47
Is 1.6.4_20120313 the version we should use now or you plan another update soon? -Rafał On 25 April 2012 12:55, Andrew Kanter <[email protected]> wrote: > Rafal, > > I am pretty sure that one file was improperly formatted and that was why I > uploaded the updated version, and I am pretty sure that I sent an email > about it when I did it... perhaps it got lost. However, for each upload we > will ensure that the UUIDs are generated in this fashion. > > Also, it seems that it might make sense to figure out a way to actually go > backwards from 1.9 to 1.6x rather than the other way. There is much more > meta data available in 1.9 which will have to be maintained (and presumably > fixed) and we won't be able to keep replacing those with each update of the > 1.6 content. I would be happy to switch to using 1.9 as the management > version, but I would need a way to get to the earlier versions which now > would be more complicated. Is it worth having someone look into this? > Anyone interested? > > Andy > > *-------------------- > Andrew S. Kanter, MD MPH > > - Director of Health Information Systems/Medical Informatics* > *Millennium Villages Project, Earth Institute, Columbia University* > *- Asst. Prof. of Clinical Biomedical Informatics and Clinical > Epidemiology* > *Columbia University* > > Email: [email protected] > Mobile: +1 (646) 469-2421 > Office: +1 (212) 305-4842 > Skype: akanter-ippnw > Yahoo: andy_kanter > > ------------------------------ > *From:* Rafal Korytkowski <[email protected]> > *To:* [email protected] > *Sent:* Wednesday, April 25, 2012 4:55 AM > *Subject:* Re: [OPENMRS-DEV] Version 1.9 Dictionary > > Andy, when I look at the openmrs_concepts_1.6.4_20120309.sql file (the one > included in 1.9-RC3) it has UUIDs in a different format already and they're > not changed when upgrading to 1.9. The file is no longer available for > download. I see only its readme. > > I've downloaded newer Openmrs_concepts_1.6.4_20120313.sql and it has UUIDs > in the correct format. Do you know what may have happened to the first file? > > Darius, we could verify that the DBs remain the same between consecutive > upgrades using any diff tool on the upgraded dbs. > > Burke, we would need to run that test as a module. It would require > extracting UUIDs from the 1.6 sql file and checking with the upgraded db. > > -Rafał > > > On 25 April 2012 04:21, Burke Mamlin <[email protected]> wrote: > > Could we use a unit test for some/all of these UUIDs to ensure that they > don't get changed again? > > -Burke > > > On Tue, Apr 24, 2012 at 1:19 PM, Darius Jazayeri > <[email protected]>wrote: > > Andy, I'm glad you caught this! > > Rafal, is the dictionary you started from a 1.6 dictionary, i.e. one that > has uuids? (If so, how did they change?) > > Also, we need to make sure that anything rows created during the upgrade > process to 1.9 (surely there are some) gets consistently assigned the same > uuid if we do the update more than once... > > -Darius > > > On Tue, Apr 24, 2012 at 9:39 AM, Andrew Kanter <[email protected]>wrote: > > Rafal/Darius/Daniel, > > When I pulled the dictionary out of the 1.9 stand alone, I noticed that > the UUIDs were not the same as those being released in the MVP/CIEL > dictionary. We replace the UUID with our initial conceptIDAAAAAA filler... > I is critical that the UUIDs are not changed during the import into 1.9. > > Andy > > *-------------------- > Andrew S. Kanter, MD MPH > > - Director of Health Information Systems/Medical Informatics* > *Millennium Villages Project, Earth Institute, Columbia University* > *- Asst. Prof. of Clinical Biomedical Informatics and Clinical > Epidemiology* > *Columbia University* > > Email: [email protected] > Mobile: +1 (646) 469-2421 > Office: +1 (212) 305-4842 > Skype: akanter-ippnw > Yahoo: andy_kanter > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > > > ------------------------------ > 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]
