The reasons we've never included such a thing is: it doesn't cover most cases. For example if you called any get methods, a column wouldn't map back properly. Including on Select * style approaches.

There's also a question of "does such a feature even need a new attribute?" or would [DataMemeber] suffice? But for anyone with currently decorated classes (e.g. for JSON serialization), this would be a breaking change and quite unexpected behavior.

In short: this would have to manifest in far more ways, and likely be in Dapper itself, not contrib. I'm not sure it meets the bar on demand, since it's nothing like the built-in behavior. It's worth taking a look at holistically in Dapper v2 though, from a view point of which bits of Contrib should migrate to Dapper core.

Closing this out to consolidate - please check out and add your thoughts to the feature design in #722!