You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to use InsertUsingStoredProcedure and UpdateUsingStoredProcedure with the same entity and configure it so that I can ignore a property on Update that is not used. Our example is using a CreatedDateTime and LastModifiedTime where both are used in the Insert procedure but then CreatedDateTime is not passed into the update procedure and we would like to ignore it for that case.
The text was updated successfully, but these errors were encountered:
AndriySvyryd
changed the title
Ignore property in Model builder entity for Update procedure only
Allow to configure a property as non-persisted only for sproc mapping
May 15, 2024
AndriySvyryd
changed the title
Allow to configure a property as non-persisted only for sproc mapping
Allow to configure a property as non-persisted only for a specific mapping
Sep 19, 2024
@AndriySvyryd Is there any way to work around this issue, so we could ignore a field, when using InsertUsingStoredProcedure? Maybe it's sufficient in a first step to remove the validation, which requires all fields to be defined as a Parameter, because this clearly doesn't hold for any entity with computed fields.
Is there a way to use InsertUsingStoredProcedure and UpdateUsingStoredProcedure with the same entity and configure it so that I can ignore a property on Update that is not used. Our example is using a CreatedDateTime and LastModifiedTime where both are used in the Insert procedure but then CreatedDateTime is not passed into the update procedure and we would like to ignore it for that case.
The text was updated successfully, but these errors were encountered: