Re: hibernate OneToMany composite key
Why is your post not in the same thread as the rest of the conversation? You
need to fix whatever you did to cause that.
comp.lang.java.programmer wrote:
Like I said I'm fairly new to hibernate [sic].
The table B has a Hibernate key on composite (x, y, z)
There is another column timestamp I could use to make up the B primary key.
"Could use"?
What *is* the primary key of the table?
Forget "could use", use what you *should* use!
So what *should* the PK be?
Again, ignoring Hibernate for a moment and just focusing on the data model.
Maybe that's the problem?
Do I need two embeddable keys MyKeyA and MyKeyB ?
I don't know. What's a "MyKeyA" and a "MyKeyB"?
When I tried to create a MyKeyB hibernate [sic] complained
1. timestamp must be insertable: false, updateable: false
2. Unable to find logical column: timestamp in table A
You provide these isolated, tiny, irrelevant snippets of information and leave
out all the important stuff. How's a person supposed to help you?
What is the table model for the two tables?
Let's forget about Hibernate for a moment and get the data model right. You
are so far from being ready to figure out the Hibernate part.
Then let's look at your object model - independently of the data model, mind you.
Only when we've completely covered those two things should we discuss how to
map one to the other.
So - what is the data model for these two tables?
--
Lew
Honi soit qui mal y pense.