Andrew,
You bug report seems more related to long table names than duplicate
columns.
I had pretty much gotten rid of my duplicate column problem (thanks to
Jason R.'s help), but then it resurfaced when I needed to add this:
Basically, it's when an entity has 0 or 1 parent entity *of the same
d Ward [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 25, 2002 3:12 PM
> To: Robertson, Jason
> Cc: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] duplicate columns created
>
>
> Will the getGroupKey() method still work on the local interfaces of my
> Group and Image ent
David,
I have found and reported a similar problem with an EJB that needs to
have a many-to-many relationship with itself.
Look at bug#532262:
http://sourceforge.net/tracker/?func=detail&aid=532262&group_id=22866&atid=376685
You should probably add your problem to this bug report... (I hadn't
ues you'd have to do another method call.
Jason
-Original Message-
From: David Ward [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 25, 2002 3:12 PM
To: Robertson, Jason
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] duplicate columns created
Will the getGroupKey() method still work
Will the getGroupKey() method still work on the local interfaces of my
Group and Image entities if I don't define them as cmp fields?
Thanks for your help,
David
--
Robertson, Jason wrote:
> At first glance it seems you have a cmp field named groupKey and a cmr field
> named groupKey, both map
At first glance it seems you have a cmp field named groupKey and a cmr field
named groupKey, both mapping to GRP_KEY. You don't need to define a cmp
field for the key when you have a relationship, so remove your definition of
groupKey as a cmp field from both your ejb-jar.xml and jbosscmp-jdbc.xml
