Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc)

Help

Home

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » teneo: same name problem using jpox

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

teneo: same name problem using jpox [message #114009]

Thu, 06 March 2008 21:12

Julia

Messages: 85
Registered: July 2009

Member

Hi Martin,

I have 2 schemas (A & B) that collide with same name for several of its
table creations. Currently using DB2 and jdk 1.4.

There appears the be several way that I can fix this problem

1) create a separate database schema for each so that the tables can exist
along side each other in the same database. But would I have to create a
separate jpoxdatastore (separate epackage & pmf) object for each schema?

2) use @Entity annotation. But I seem to recall that I will need jdk 1.5
for this. Upgrading will cause other problems.

3) Use QualifyingEntityNameStrategy extensions to add prefix. One of my
collegues tried this method but still had issues due to the complexities
of our schemas and DB2 column limitations.

What would be your best suggestion?

Julia

Report message to a moderator

Re: teneo: same name problem using jpox [message #114021 is a reply to message #114009]

Thu, 06 March 2008 21:52

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Hi Julia,
See my answers inline.

gr. Martin

Julia wrote:
> Hi Martin,
>
> I have 2 schemas (A & B) that collide with same name for several of its
> table creations. Currently using DB2 and jdk 1.4.
>
> There appears the be several way that I can fix this problem
>
> 1) create a separate database schema for each so that the tables can
> exist along side each other in the same database. But would I have to
> create a separate jpoxdatastore (separate epackage & pmf) object for
> each schema?
MT>> If you choose this solution then you would need to create a separate jpoxdatastore for each.
However if the epackages refer to eachother then this won't work.

>
> 2) use @Entity annotation. But I seem to recall that I will need jdk 1.5
> for this. Upgrading will cause other problems.
MT>> The @Entity is also supported in Teneo 0.7.5. You can also use the @Table annotation.

>
> 3) Use QualifyingEntityNameStrategy extensions to add prefix. One of my
> collegues tried this method but still had issues due to the complexities
> of our schemas and DB2 column limitations.
MT>> Normally this should solve any name clashes (assuming that the epackage prefix is unique. Just
let me know what issues you encounter.

> What would be your best suggestion?
>
> Julia
>

--

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

Report message to a moderator

Re: teneo: same name problem using jpox [message #615619 is a reply to message #114009]

Thu, 06 March 2008 21:52

Martin Taal

Messages: 5468
Registered: July 2009

Senior Member

Report message to a moderator

Previous Topic:	teneo: same name problem using jpox
Next Topic:	Loading a GMF diagram resource from Hibernate

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jun 26 08:03:16 GMT 2022

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter