[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipselink-users] CASCADE DELETE at DB-side
- From: James Sutherland <jamesssss@xxxxxxxxx>
- Date: Fri, 17 Dec 2010 06:06:10 -0800 (PST)
- Delivered-to: email@example.com
In the current development stream on EclipseLink (trunk/2.2) there is a
@CascadeOnDelete annotation for declaring the delete cascade constraint.
In the released version of EclipseLink you could,
- use cascade in JPA instead of the constraint
- use cascade in JPA and on the database, EclipseLink will issue the delete,
but should have no affect
- use cascade only in the database, EclipseLink will not issue the SQL, but
object may be left in shared cache (you could invalidate it if you wished)
BÃlint KrivÃn wrote:
> Hello to the community!
> I'm wondering if I'm using ON DELETE CASCADE option on my foreign key,
> it be reflected in EclipseLink objects, or how should I warn EclipseLink
> about this possibility? Is there an annotation for it? Thanks!
> BÃlint KrivÃn
http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
EclipseLink , http://www.oracle.com/technology/products/ias/toplink/
Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink ,
Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence
Blog: http://java-persistence-performance.blogspot.com/ Java Persistence
View this message in context: http://old.nabble.com/CASCADE-DELETE-at-DB-side-tp30425056p30481142.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.