Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community Forums[CDO] Productive Use and Schema Evolution
https://www.eclipse.org/forums/index.php/mv/msg/368748/899173/#msg_899173
I want to extend my application with collaboration capabilities. For that purpose, I am thinking about migrating from XMI files to CDO/Teneo.
Is CDO already applicable for productive use or is it still a development version?
And what I think what is very important: How do you handle the evolution of the database schema? For example I have several models stored and EMF gets updated to a newer version. Is the schema changed too?
Regards,
Tex]]>Tex Iano2012-07-30T20:42:03-00:00Re: [Teneo] Productive Use and Schema Evolution
https://www.eclipse.org/forums/index.php/mv/msg/368748/899180/#msg_899180
> Hi,
>
> I want to extend my application with collaboration capabilities. For
> that purpose, I am thinking about migrating from XMI files to Teneo.
> Is Teneo already applicable for productive use or is it still a
> development version?
>
Yes. Teneo is stable and we are using it in a number of RCP projects
very successfully!
> And what I think what is very important: How do you handle the evolution
> of the database schema? For example I have several models stored and EMF
> gets updated to a newer version. Is the schema changed too?
> Regards,
>
Well DB-Schema-Evolution is not a simple thing. Hibernate has some
schema evolution but we are doing the schema evolution by hand.
Our process is like this:
a) Generate the hbm.xml from the ecore
b) Generate the DDL from the hbm.xml using Hibernate
c) Store the DDL in the VCS
d) Update the .ecore
e) => back to step a)
f) Diff the change in the DDL and write an alter script by hand
Tom]]>Thomas Schindl2012-07-30T21:22:13-00:00Re: [Teneo] Productive Use and Schema Evolution
https://www.eclipse.org/forums/index.php/mv/msg/368748/899245/#msg_899245
Yes indeed Teneo is quite stable, a new version of EMF normally does not change the database schema. If I find a really
breaking issue in Teneo which results in a difference in db schema generation (to solve this issue) then I provide an
option for backward compatibility support.
As Tom describes, if you have extensive changes in your model then the Hibernate is not capable of updating the db
schema correctly. New tables and columns are normally handled automatically by hibernate, deleting columns/tables is not
possible (but most of the time less relevant when updating models).
gr. Martin
On 07/30/2012 11:22 PM, Tom Schindl wrote:
> Am 30.07.12 22:42, schrieb Tex Iano:
>> Hi,
>>
>> I want to extend my application with collaboration capabilities. For
>> that purpose, I am thinking about migrating from XMI files to Teneo.
>> Is Teneo already applicable for productive use or is it still a
>> development version?
>>
>
> Yes. Teneo is stable and we are using it in a number of RCP projects
> very successfully!
>
>> And what I think what is very important: How do you handle the evolution
>> of the database schema? For example I have several models stored and EMF
>> gets updated to a newer version. Is the schema changed too?
>> Regards,
>>
>
> Well DB-Schema-Evolution is not a simple thing. Hibernate has some
> schema evolution but we are doing the schema evolution by hand.
>
> Our process is like this:
> a) Generate the hbm.xml from the ecore
> b) Generate the DDL from the hbm.xml using Hibernate
> c) Store the DDL in the VCS
> d) Update the .ecore
> e) => back to step a)
> f) Diff the change in the DDL and write an alter script by hand
>
> Tom
>