Skip to content

TypeHandlerPrecedence

Namespace: MJCZone.DapperMatic.TypeMapping

Assembly: MJCZone.DapperMatic

Summary

Defines how type handler registration should handle conflicts with existing handlers.

Inheritance

Base Class: Enum

sealed public

Contents

Enum Members (3)

Enum Members

NameValueDescription
SkipIfExists0Skip registration if handler already exists (don't override user's handlers). This is the safest option that respects user customizations.
OverrideExisting1Override existing handlers (DapperMatic handlers take precedence). Use this if you want DapperMatic handlers to always be used.
ThrowIfExists2Throw exception if handler already exists (fail fast on conflicts). Use this during development to detect handler conflicts early.