C# 클래스 NHibernate.Engine.CascadeStyle

상속: ISerializable

파일 보기 프로젝트 열기: nhibernate/nhibernate-core 1 사용 예제들

공개 프로퍼티들

프로퍼티	타입	설명
All	CascadeStyle
AllDeleteOrphan	CascadeStyle
Delete	CascadeStyle
DeleteOrphan	CascadeStyle
Evict	CascadeStyle
Lock	CascadeStyle
Merge	CascadeStyle
None	CascadeStyle
Persist	CascadeStyle
Refresh	CascadeStyle
Replicate	CascadeStyle
Update	CascadeStyle

공개 메소드들

메소드	설명
DoCascade ( NHibernate.Engine.CascadingAction action ) : bool	For this style, should the given action be cascaded?
GetCascadeStyle ( string cascade ) : CascadeStyle	Factory method for obtaining named cascade styles
ReallyDoCascade ( NHibernate.Engine.CascadingAction action ) : bool	Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches... For this style, should the given action really be cascaded? The default implementation is simply to return {@link #doCascade}; for certain styles (currently only delete-orphan), however, we need to be able to control this separately.

비공개 메소드들

메소드	설명
CascadeStyle ( ) : System	package-protected constructor
ISerializable ( SerializationInfo info, StreamingContext context ) : void

메소드 상세

DoCascade() 공개 추상적인 메소드

For this style, should the given action be cascaded?

public abstract DoCascade ( NHibernate.Engine.CascadingAction action ) : bool
action	NHibernate.Engine.CascadingAction	The action to be checked for cascade-ability.
리턴	bool

GetCascadeStyle() 공개 정적인 메소드

Factory method for obtaining named cascade styles

public static GetCascadeStyle ( string cascade ) : CascadeStyle
cascade	string	The named cascade style name.
리턴	CascadeStyle

ReallyDoCascade() 공개 메소드

Probably more aptly named something like doCascadeToCollectionElements(); it is however used from both the collection and to-one logic branches...

For this style, should the given action really be cascaded? The default implementation is simply to return {@link #doCascade}; for certain styles (currently only delete-orphan), however, we need to be able to control this separately.

public ReallyDoCascade ( NHibernate.Engine.CascadingAction action ) : bool
action	NHibernate.Engine.CascadingAction	The action to be checked for cascade-ability.
리턴	bool

프로퍼티 상세

All 공개적으로 정적으로 프로퍼티

save / delete / update / evict / lock / replicate / merge / persist

public static CascadeStyle,NHibernate.Engine All
리턴	CascadeStyle

AllDeleteOrphan 공개적으로 정적으로 프로퍼티

save / delete / update / evict / lock / replicate / merge / persist + delete orphans

public static CascadeStyle,NHibernate.Engine AllDeleteOrphan
리턴	CascadeStyle

Delete 공개적으로 정적으로 프로퍼티

delete

public static CascadeStyle,NHibernate.Engine Delete
리턴	CascadeStyle

DeleteOrphan 공개적으로 정적으로 프로퍼티

delete + delete orphans

public static CascadeStyle,NHibernate.Engine DeleteOrphan
리턴	CascadeStyle

Evict 공개적으로 정적으로 프로퍼티

evict

public static CascadeStyle,NHibernate.Engine Evict
리턴	CascadeStyle

Lock 공개적으로 정적으로 프로퍼티

lock

public static CascadeStyle,NHibernate.Engine Lock
리턴	CascadeStyle

Merge 공개적으로 정적으로 프로퍼티

merge

public static CascadeStyle,NHibernate.Engine Merge
리턴	CascadeStyle

None 공개적으로 정적으로 프로퍼티

no cascades

public static CascadeStyle,NHibernate.Engine None
리턴	CascadeStyle

Persist 공개적으로 정적으로 프로퍼티

create

public static CascadeStyle,NHibernate.Engine Persist
리턴	CascadeStyle

Refresh 공개적으로 정적으로 프로퍼티

refresh

public static CascadeStyle,NHibernate.Engine Refresh
리턴	CascadeStyle

Replicate 공개적으로 정적으로 프로퍼티

replicate

public static CascadeStyle,NHibernate.Engine Replicate
리턴	CascadeStyle

Update 공개적으로 정적으로 프로퍼티

save / update

public static CascadeStyle,NHibernate.Engine Update
리턴	CascadeStyle