Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » teneo - persisting the ecore itself (FAQ)
| teneo - persisting the ecore itself (FAQ) [message #57808] |
Mon, 16 October 2006 18:22  |
Eclipse User |
|
|
|
Hi Martin (and others),
I know that this or similar have been asked before. But just out of
curiosity, is persisting of the ecore itself fully supported now?
I'm asking because I just experimentally added an association from my
domain model to the EClass and added the EcorePackage.eINSTANCE to the
EPackages to be mapped to hibernate and surprisingly it worked! At
least, ecore related tables have been created in the DB, like "EClass",
"EPackage" and others. Will those be fully working or with restrictions?
Has anybody tested this already?
I'm asking because the architecture of the application that I am going
to build kind of depends on those capabilities. If this is not an
option, I would have to help myself with EClass IDs which I had to
resolve in a derived association for instance. If teneo already had the
capabilities, I could use them directly! That would make it very much
easier...
Regards
Andre
|
|
| |
| Re: teneo - persisting the ecore itself (FAQ) [message #57856 is a reply to message #57832] |
Mon, 16 October 2006 18:54  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Andre,
Yeah, Martin has done a great job, hasn't he! ;-)
Andre Pareis wrote:
> I'm really impressed. I just gave it a try and it was absolutely no
> problem to persist the ecore itself plus my own packages. Martin, this
> is really really a great piece of work that you've created for us
> here... :)
>
> Andre Pareis schrieb:
>> Hi Martin (and others),
>>
>> I know that this or similar have been asked before. But just out of
>> curiosity, is persisting of the ecore itself fully supported now?
>>
>> I'm asking because I just experimentally added an association from my
>> domain model to the EClass and added the EcorePackage.eINSTANCE to
>> the EPackages to be mapped to hibernate and surprisingly it worked!
>> At least, ecore related tables have been created in the DB, like
>> "EClass", "EPackage" and others. Will those be fully working or with
>> restrictions? Has anybody tested this already?
>>
>> I'm asking because the architecture of the application that I am
>> going to build kind of depends on those capabilities. If this is not
>> an option, I would have to help myself with EClass IDs which I had to
>> resolve in a derived association for instance. If teneo already had
>> the capabilities, I could use them directly! That would make it very
>> much easier...
>>
>> Regards
>> Andre
|
|
|
| Re: teneo - persisting the ecore itself (FAQ) [message #57878 is a reply to message #57856] |
Tue, 17 October 2006 05:37 |
| Eclipse User |
|
|
|
Thanks for the kudos :-)!
I actually tested this before and on mysql 4.1 I got an exception because hibernate tried to do a
join with 61 tables which it apparently was not able to handle. So the queries may not be that
efficient. On the other hand model data is normally very small (in database terms).
With microsoft sql server my test (storing and retrieving the library ecore model) worked fine.
When I tested it it also stored the ecore model itself in the database (as the ecore model is
represented in ecore also).
gr. Martin
Ed Merks wrote:
> Andre,
>
> Yeah, Martin has done a great job, hasn't he! ;-)
>
>
> Andre Pareis wrote:
>> I'm really impressed. I just gave it a try and it was absolutely no
>> problem to persist the ecore itself plus my own packages. Martin, this
>> is really really a great piece of work that you've created for us
>> here... :)
>>
>> Andre Pareis schrieb:
>>> Hi Martin (and others),
>>>
>>> I know that this or similar have been asked before. But just out of
>>> curiosity, is persisting of the ecore itself fully supported now?
>>>
>>> I'm asking because I just experimentally added an association from my
>>> domain model to the EClass and added the EcorePackage.eINSTANCE to
>>> the EPackages to be mapped to hibernate and surprisingly it worked!
>>> At least, ecore related tables have been created in the DB, like
>>> "EClass", "EPackage" and others. Will those be fully working or with
>>> restrictions? Has anybody tested this already?
>>>
>>> I'm asking because the architecture of the application that I am
>>> going to build kind of depends on those capabilities. If this is not
>>> an option, I would have to help myself with EClass IDs which I had to
>>> resolve in a derived association for instance. If teneo already had
>>> the capabilities, I could use them directly! That would make it very
>>> much easier...
>>>
>>> Regards
>>> Andre
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: teneo - persisting the ecore itself (FAQ) [message #594166 is a reply to message #57808] |
Mon, 16 October 2006 18:31 |
| Eclipse User |
|
|
|
I'm really impressed. I just gave it a try and it was absolutely no
problem to persist the ecore itself plus my own packages. Martin, this
is really really a great piece of work that you've created for us here... :)
Andre Pareis schrieb:
> Hi Martin (and others),
>
> I know that this or similar have been asked before. But just out of
> curiosity, is persisting of the ecore itself fully supported now?
>
> I'm asking because I just experimentally added an association from my
> domain model to the EClass and added the EcorePackage.eINSTANCE to the
> EPackages to be mapped to hibernate and surprisingly it worked! At
> least, ecore related tables have been created in the DB, like "EClass",
> "EPackage" and others. Will those be fully working or with restrictions?
> Has anybody tested this already?
>
> I'm asking because the architecture of the application that I am going
> to build kind of depends on those capabilities. If this is not an
> option, I would have to help myself with EClass IDs which I had to
> resolve in a derived association for instance. If teneo already had the
> capabilities, I could use them directly! That would make it very much
> easier...
>
> Regards
> Andre
|
|
|
| Re: teneo - persisting the ecore itself (FAQ) [message #594178 is a reply to message #57832] |
Mon, 16 October 2006 18:54 |
| Eclipse User |
|
|
|
Andre,
Yeah, Martin has done a great job, hasn't he! ;-)
Andre Pareis wrote:
> I'm really impressed. I just gave it a try and it was absolutely no
> problem to persist the ecore itself plus my own packages. Martin, this
> is really really a great piece of work that you've created for us
> here... :)
>
> Andre Pareis schrieb:
>> Hi Martin (and others),
>>
>> I know that this or similar have been asked before. But just out of
>> curiosity, is persisting of the ecore itself fully supported now?
>>
>> I'm asking because I just experimentally added an association from my
>> domain model to the EClass and added the EcorePackage.eINSTANCE to
>> the EPackages to be mapped to hibernate and surprisingly it worked!
>> At least, ecore related tables have been created in the DB, like
>> "EClass", "EPackage" and others. Will those be fully working or with
>> restrictions? Has anybody tested this already?
>>
>> I'm asking because the architecture of the application that I am
>> going to build kind of depends on those capabilities. If this is not
>> an option, I would have to help myself with EClass IDs which I had to
>> resolve in a derived association for instance. If teneo already had
>> the capabilities, I could use them directly! That would make it very
>> much easier...
>>
>> Regards
>> Andre
|
|
|
| Re: teneo - persisting the ecore itself (FAQ) [message #594192 is a reply to message #57856] |
Tue, 17 October 2006 05:37 |
| Eclipse User |
|
|
|
Thanks for the kudos :-)!
I actually tested this before and on mysql 4.1 I got an exception because hibernate tried to do a
join with 61 tables which it apparently was not able to handle. So the queries may not be that
efficient. On the other hand model data is normally very small (in database terms).
With microsoft sql server my test (storing and retrieving the library ecore model) worked fine.
When I tested it it also stored the ecore model itself in the database (as the ecore model is
represented in ecore also).
gr. Martin
Ed Merks wrote:
> Andre,
>
> Yeah, Martin has done a great job, hasn't he! ;-)
>
>
> Andre Pareis wrote:
>> I'm really impressed. I just gave it a try and it was absolutely no
>> problem to persist the ecore itself plus my own packages. Martin, this
>> is really really a great piece of work that you've created for us
>> here... :)
>>
>> Andre Pareis schrieb:
>>> Hi Martin (and others),
>>>
>>> I know that this or similar have been asked before. But just out of
>>> curiosity, is persisting of the ecore itself fully supported now?
>>>
>>> I'm asking because I just experimentally added an association from my
>>> domain model to the EClass and added the EcorePackage.eINSTANCE to
>>> the EPackages to be mapped to hibernate and surprisingly it worked!
>>> At least, ecore related tables have been created in the DB, like
>>> "EClass", "EPackage" and others. Will those be fully working or with
>>> restrictions? Has anybody tested this already?
>>>
>>> I'm asking because the architecture of the application that I am
>>> going to build kind of depends on those capabilities. If this is not
>>> an option, I would have to help myself with EClass IDs which I had to
>>> resolve in a derived association for instance. If teneo already had
>>> the capabilities, I could use them directly! That would make it very
>>> much easier...
>>>
>>> Regards
>>> Andre
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
Goto Forum:
Current Time: Sat May 03 15:57:35 EDT 2025
Powered by FUDForum. Page generated in 0.05099 seconds |
Home