I see. I specifically had problems with relation tables though. I had
columns generated as _attribute_OTHERTABLENAME and the first _
didn't make
it through Derby. Hence the necessary usage of @ElementJoinColumn.
Are these mandated by the spec as well?
Yes. And as I said, there are standard
I see. I specifically had problems with relation tables though. I had
columns generated as _attribute_OTHERTABLENAME and the first _ didn't make
it through Derby. Hence the necessary usage of @ElementJoinColumn.
Are these mandated by the spec as well?
On 1/15/07, Abe White <[EMAIL PROTECTED]> wr
I don't feel pre-fixing with '_' for member level attributes is really
necessary, particularly if you're using an IDE. I can see how it would
help someone using only vi or emacs recognize what was what, but with
the color code and hotkeys and quick-clicking available in IDE's, it
just doesn't
I think it could be nicer and a bit easier if OpenJPA was
automatically
eliminating the first _ from attribute names to build its default
coumn
names, don't you think?
The default column names are mandated by the JPA specification. And
unless you're using OpenJPA-specific mappings, you sh
Hi,
We're using _attributes notations for instance attributes in Ode and I've
found slight problems with it in OpenJPA. If you use this notation the
default column names chosen by OpenJPA will start with _ which forces you to
use @Column and @ElementJoinColumn (unfortunately OpenJP
