Eclipse Community Forums: EMF » [CDO] Table naming strategy for DerbyStore

Help

Home

Home » Modeling » EMF » [CDO] Table naming strategy for DerbyStore

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

[CDO] Table naming strategy for DerbyStore [message #427479]

Wed, 18 February 2009 23:14

Kai Schlamp

Messages: 344
Registered: July 2009

Senior Member

Hello.

Is there some kind of table naming strategy for the DerbyStore.
I'd like to avoid conflicts when two EClasses in separate models have
the same name, but are stored in the same Derby database.

For example, when storing two EClasses (in different models) named
PropertyKey in the same database, I get the following error:
Caused by: org.eclipse.net4j.util.transaction.TransactionException:
Rollback in DBStore: org.eclipse.net4j.db.DBException: DBTable exists:
PropertyKey

Teneo for example has an EntityNameStrategy Extension that allows to set
it to QualifyingEntityNameStrategy.
This creates an entity name by prefixing the eclass name with the
epackage nsprefix or the name of the epackage. This always results in
unique entity names.

Are there any solutions of that kind for the DerbyStore?

Best regards,
Kai

Report message to a moderator

Re: [CDO] Table naming strategy for DerbyStore [message #427484 is a reply to message #427479]

Thu, 19 February 2009 06:08

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Kai,

The info may be a bit hidden in the wiki:
http://wiki.eclipse.org/CDO_Server_Configuration_Reference#P roperty_qualifiedNames
Please let me know if tat is not what you were looking for.

Cheers
/Eike

----
http://thegordian.blogspot.com

Kai Schlamp schrieb:
> Hello.
>
> Is there some kind of table naming strategy for the DerbyStore.
> I'd like to avoid conflicts when two EClasses in separate models have
> the same name, but are stored in the same Derby database.
>
> For example, when storing two EClasses (in different models) named
> PropertyKey in the same database, I get the following error:
> Caused by: org.eclipse.net4j.util.transaction.TransactionException:
> Rollback in DBStore: org.eclipse.net4j.db.DBException: DBTable exists:
> PropertyKey
>
> Teneo for example has an EntityNameStrategy Extension that allows to
> set it to QualifyingEntityNameStrategy.
> This creates an entity name by prefixing the eclass name with the
> epackage nsprefix or the name of the epackage. This always results in
> unique entity names.
>
> Are there any solutions of that kind for the DerbyStore?
>
> Best regards,
> Kai

Cheers
/Eike

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

Report message to a moderator

Re: [CDO] Table naming strategy for DerbyStore [message #427488 is a reply to message #427484]

Thu, 19 February 2009 12:14

Kai Schlamp

Messages: 344
Registered: July 2009

Senior Member

Hy Eike.

Yes, that was it what I was looking for. Thank you.

Kai

> The info may be a bit hidden in the wiki:
> http://wiki.eclipse.org/CDO_Server_Configuration_Reference#P roperty_qualifiedNames
>
> Please let me know if tat is not what you were looking for.

Report message to a moderator

Previous Topic:	Synchronize to EObjects completely
Next Topic:	How to create a View to Interact with EMF Model

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 10:18:26 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter