On Tue, 28 Jun 2011 00:15:36 +0200, Steve Ebersole <st...@hibernate.org> wrote:
>>> First, I think CascadeType should be changed up a bit. Currently it >>> contains some "aggregate" values (ALL, ALL_DELETE_ORPHAN). I'd like to >>> keep this limited to just the "atomic" cascade-types. Rather than the >>> map lookups here based on the enum value, I'd much rather see the enum >>> expose that "alternate value". For example: >>> https://gist.github.com/1044751 >> >> Ok. The cascade style to cascade type map is new to me anyway. >> Btw, why do you prefer the "enum expose that "alternate value"" >> approach? > > I don't know to be honest. It just "feels" right to me (remember I have > a BA, not a BS lol). I think because it is a one-to-one corelation. Ok, more of a taste thing. I thought I missed something :-) _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
