-
Notifications
You must be signed in to change notification settings - Fork 132
Bug: IPropertyHandler not being called #514
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingdeployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releasefixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.todoThings to be done in the futureThings to be done in the future
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingdeployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releasefixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.todoThings to be done in the futureThings to be done in the future
I'm referencing this issue #437 and, yes, I'm aware of the pitfalls of doing string to Guid conversion. DB design is not under my control so I can only consume it.
First of all I've switched to MDS in the sample and have discovered another unrelated issue as reported here #513.
Now the default sample works but in a scenario where you use map attribute the property handler is not being called. As I mentioned the db design is not under my control I am merely a consumer (third party). So consider the following example.
var result = connection.Query<DemoUpsertObj>(p => p.Id == recordId).FirstOrDefault();No results will be returned. Remove the map attribute or just lowercase the property and a match will be returned.
Modified sample project:
RepoDbIssue437.zip