Cheers
all,
Why can you not have a regular JoinColumn with
a SecondaryTable?
Why only PrimaryKeyJoinColumns?
Currently
only PK's are supported for joining to secondary tables.
Sect. 9.1.6
- Why is JoinColumn
targetted to Type? Where can
it be used in that context? JoinColumn*s* is not targetted to Type, so what is
different?
Yes, TYPE has been removed. Thanks.
Sect. 9.1.7
- "Composite foreign keys are supported by means of the JoinColumns
annotation. The JoinColumns
annotation groups JoinColumn annotations for the same relationship *or table association*." Can JoinColumn/s be
used for table associations?
We will fix this. Thanks.
Sect. 9.1.30
- Table 21
- What is the distinction between the following: "The same name
as the primary key column of the superclass (JOINED mapping strategy)"
(default for name)
and "The same name as the primary key column *of the primary table* of the
superclass (JOINED mapping strategy)" (default for referencedColumnName)?
And if they are the same, shouldn't they read the same?
- These should read the same: "the same name as the primary
key column of the primary table (SecondaryTable
mapping)" (default for name) and "the
same name as *the name of* the
primary key column of the primary table (SecondaryTable mapping)"
(default for referencedColumnName)?
The "the name of" is superfluous and makes the reader wonder if there
is a distinction.
Okay, thanks.
Sect. 9.1.12
- What are the requirements on the PK class in this example? (What
does it look like?)
See 2.1.4.
Sect. 9.1.13
- What are the requirements on the PK class in this example? (What
does it look like?)
See 2.1.4.
Thanks,
- Paul
