[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipselink-users] UnidirectionalOneToManyMapping yeesh!
|
The answers are inline
----- Original Message -----
Sent: Thursday, October 30, 2008 3:43
PM
Subject: [eclipselink-users]
UnidirectionalOneToManyMapping yeesh!
I am thinking
that UnidirectionalOneToManyMapping is a good name: it describes
exactly what the mapping is.
Also I am thinking that it's a
working document the main purpose of which
is to communicate requirements,
pinpoint possible problems, suggest alternative solutions for them etc.
-
but not necessarily spend precious
time on every last detail.
UnidirectionalOneToManyMapping has
been added to the code,
but UnidirectionalOneToManyRelationMaintanenceMode hasn't
been.
In
> my experience long names are
usually a strong indication that something more
> fundamental is
wrong.
In my experience they are
not.
>
> 2)
UnidirectionalOneToManyRelationMaintanenceMode.RemoveNowait versus
>
RemoveNoWait... It's annoying when people misuse camelCase :)
>
> 3) In my view, you are better off
defining a new OneToMany in a new package
> than creating these new
classes.