OK. Not really sure what to do at this point then. I have tried the procedure several times. My categoryoptioncombo table is defined as follows
CREATE TABLE categoryoptioncombo ( categoryoptioncomboid integer NOT NULL, CONSTRAINT categoryoptioncombo_pkey PRIMARY KEY (categoryoptioncomboid) ) WITH ( OIDS=FALSE ); Does not seem to have a uuid property. Is this the right table? On Wed, Mar 2, 2011 at 3:30 PM, Jo Størset <stor...@gmail.com> wrote: > > Den 2. mars 2011 kl. 19.33 skrev Jason Pickering: > >> Thanks for this Jo, but I think this is not the issue. A bit more detail. > > > <snip/> > > This sounds about right. I guess I only added uuids that are missing for data > elements, while optioncombo has also gotten uuid added in the hibernate > mapping (it already had uuid as a property). I thought hibernate would take > care of updating by itself, and have not noticed any trouble myself (on quite > a lot of databases). But I'm not the most knowledgable about hibernate, so > there might be subtle details I don't know about. > > This uuid is not critical for now (as long as nobody needs to post datavalues > with combos to the api), so it can be removed from the branch if finding > another solution is difficult. > > Jo -- Jason P. Pickering email: jason.p.picker...@gmail.com tel:+260974901293 _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp