Hello Team,
What do you think about adding "on-delete" attribute to
"key-many-to-one-element" type in HBM mapping? This would allow
generation of "ON DELETE CASCADE" clause.
Context: "HHH-7807 - Deleting Revision Entity" and "HHH-8052 -
Possibility to deleted audits/revisions in an orderly way".
I'm planning on working on OGM-151. Fine with everyone?
That will likely be my last before I move back to BVAL and close the
final issues there.
Emmanuel
On Tue 2013-03-05 19:04, Sanne Grinovero wrote:
> Nice!
> n+1 is something Hibernate Search has to deal with too, that's why I
> was interested
it's ok for me
Davide
On Wed, Mar 6, 2013 at 3:28 PM, Emmanuel Bernard wrote:
> I'm planning on working on OGM-151. Fine with everyone?
> That will likely be my last before I move back to BVAL and close the
> final issues there.
>
> Emmanuel
>
> On Tue 2013-03-05 19:04, Sanne Grinovero wrote:
>>
I've successfully implemented OGM-151 for EntityKey which is the one we
need to move OGM-273 forward for now.
I am trying to implement it for AssociationKey but caching here is
significantly harder as data is cross reference across associations.
Sanne, when you worked on the profiling of OGM, do y
