-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: un-compounding compund key during reverse engineering?
PostPosted: Mon Jan 30, 2006 6:36 pm 
Beginner
Beginner

Joined: Wed Nov 02, 2005 3:29 pm
Posts: 20
I have a strange situation that I'm trying to find an easy workaround
for. I'm working with 5 tables, with various FK.
Due to some strange application programming one table
has inconsistet data that is "used" to reference a second
table

The default reverse process generates:

<many-to-one name="orgUnitIdAndorgUnitType" class="ca.ubc.nmc.contacts.db.NcOrgUnit" fetch="select">
<column name="ORG_UNIT_ID" length="10" />
<column name="ORG_UNIT_TYPE" length="4" />
</many-to-one>

Is there a way that I use my own reverse stragtegy to force the
FK columns as just simple string colums rather than the
compound key they are supposed to be?

I realize that I can do it by running the reverse process twice
and excluding the appropriate tables, but that creates maintenance
problems if the reverse has to be run in the furture.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.