MapperSaveOptions Enumeration |
Namespace:
NetQuarry.Data
Assembly:
EAP.Core (in EAP.Core.dll) Version: 2.0.0.0 (4.6.8.0)
Syntax [FlagsAttribute]
public enum MapperSaveOptions
<FlagsAttribute>
Public Enumeration MapperSaveOptions
Members
| Member name | Value | Description |
---|
| RequiredExceptLegacy | 1 |
This mapper includes fields currently marked Required, but that were not originally so marked.
The save should be performed even if one or more such fields are null, provided that each such field was already null.
This handles the case where a field is newly marked as required, but there are existing records in the DB that
were created when the field was NOT required, and the caller wants to allow changes to those records without requiring
this field NOW be populated. Note, however, once such a field IS set, we don't want to allow the user to clear it!
This applies to updates only.
You can also set the field's RequiredExceptLegacy FieldBehaviorAttribute to get this
behaviour on all updates.
|
| SmartDupeCheck | 2 |
Do not perform duplicate checking (per the fields' DupeCheck attributes) unless one or more
of the fields involved in the DupeCheck filter construction has changed.
This applies to updates only.
|
| NoRowRequery | 4 |
Do not perform a post-save row requery.
By default the current record is requeried following a save in order to pick up changes due to triggers and calculated columns.
This has the same effect as setting NoRowRequery except that it applies only to this Save(MapperSaveOptions) call.
|
| NoAudit | 8 |
Do not fire audit events on this mapper when performing the save.
See AuditInsert(IMapper, EAPEventArgs),
AuditUpdate(IMapper, EAPEventArgs),
AuditDelete(IMapper, EAPEventArgs).
|
| RedirectFollows | 16 |
A redirect will be performed immediately following the save. This lets the mapper know that it can avoid post-save rendering where possible.
|
| IgnoreRequired | 32 |
The save should ignore requiredness on all fields (ignoring Required). This is helpful when creating records programatically.
In general, this should be used with care as it may result in records having unexpected null values for required columns.
|
| AlwaysAttemptSave | 64 |
Normally a mapper will not attempt a save unless it is Dirty. If it is not dirty, the mapper will not even fire any
RowBeforeInsert or RowBeforeUpdate event.
You can set this attribute to cause the mapper to attempt a save even when it is not Dirty and to fire the appropriate
Before event.
Forcing a save attempt (and the corresponding Before event to fire) is useful when there is extension logic handling the event that
needs to be performed regardless of the dirty state and/or that will cause the mapper to become dirty (thereby allowing the save to be performed).
Note that if the mapper is still not dirty following the Before event, the save will not be performed, but the corresponding
RowAfterInsert or RowAfterUpdate event will be fired.
|
| ImprovedRowRequery | 128 |
If a RowRequery is performed, save using the improved IMapper RowRequery mechanism.
Since the improved mechanism is now the default behaviour, this option has no effect unless a system-side or mapper-specific backward compatibility option is set.
See Save(MapperSaveOptions) for a discussion of the old vs. improved RowRequery mechanisms.
|
See Also