Eclipse Community Forums: EMF » [CDO] How do I force an update to my model package on the server?

Help

Home

Home » Modeling » EMF » [CDO] How do I force an update to my model package on the server?

Show: Today's Messages :: Show Polls :: Message Navigator

[CDO] How do I force an update to my model package on the server? [message #1841697]

Tue, 25 May 2021 23:23

Warwick Burrows

Messages: 132
Registered: July 2009
Location: Austin, TX

Senior Member

I've made changes to my model for the first time in a long time but even though the client is registering the packages in the client as part of client init and connection setup with the server, the model package in the "blob" column in the CDO_PACKAGE_UNITS table isn't being updated. When I unzip the blob contents from the table and view the ResourceContents file within I can see that it is the old version of the model without the new EClasses defined.

I've also tried using the initialPackage property from the cdo-server.xml but I don't see an entry in the EPackageRegistry map for my model. in fact neither of my models appear in that map.

Should I be using the model nsURI to version my model? e.g. if my model's nsURI is currently "http://blah/mymodel/1.0" do I need to change the nsURI in the ecore model file that I use to be "http://blah/mymodel/1.1", then regen the model code and my client and load that new model package from the client? I mean I've changed the model code and I'm already loading a different model package but its not being registered in the server. If it change the nsURIj is it normal/safe for me to have two versions of the same model with 90% of the same model classes loaded in CDO? I don't see a client API to remove an model package.

Report message to a moderator

Re: [CDO] How do I force an update to my model package on the server? [message #1841814 is a reply to message #1841697]

Mon, 31 May 2021 06:42

Eike Stepper

Messages: 6690
Registered: July 2009

Senior Member

Currently there's nothing in CDO to directly support you with your model evolution. Even though it's probably the most wanted new feature, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=256856 , there has never been funding to get it done. Your best option is probably to export all instance data, transform the export to the new model version, and then import it into a new DB.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Previous Topic:	[CDO] CDOModelUtil lookup for coreTypes varies between server startup and client call
Next Topic:	import org.eclipse cannot be resolved

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Nov 08 22:09:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter