I get
net.sf.hibernate.MappingException: Repeated column in mapping for collection: co
m.studentuniverse.farefilter.persistent.Fares.priceCostCalc column: prcolo_id
at net.sf.hibernate.collection.CollectionPersister.checkColumnDuplicatio
n(CollectionPersister.java:838)

for the following mapping. Is there a way to let it use a column for more than one entry (or did I miss what the real problem is?)

How is it semantically correct to have an association table with just one column!?

This makes it a one-to-one association!

I think I'm just way off and have to figure this out more.

What I have is table A with prcolo_id, and table B also with this id. Table B can have n number of records, so it sounds like a many to one.

I get confused as to what tables the "column" attributes refer to. What I need to figure out is how to tell it use table a column as the key, and get the collection from table b's corresponding column.

I tried one to many but it won't take a column attribute, I think it's only assuming using the primary key for my table B, and I can't use something different, or figure out how to specify that yet.

You do NOT need to specify the primary key in a one-to-many mapping! Hibernate is not stupid. It knows what the damn primary key column of a class is!


The rules are quite simple:

The <joined-subclass>, <class>, <set>, <list>, etc all define a table attribute. Any column names that appear inside one of these elements refers to _that_table_ (and no other table!)

I am talking about this very restriction, if I understand it.

If I map class A to B one to many, the reference back to A must be A's ID, nothing else, correct?

Say A is a customer, and B are invoices. It makes sense the B will have a key for customer number.

But if A also has a messageID, and C is a message table (X lines of message for a messageID). Is it possible for me to make a one to many mapping that says a.messageID to c.messageID to get a collection of the messages for a customer?

after looking some more, what I needed was a many to many, but without the interim table, which hibernate doesn't do. So I'll load in this collection via a joined query, which should solve it well enough.
Legacy data!