Scan destination safety (like in sqlx)

[josephbuchma]

Is something like this possible in jet?

By default, StructScan will return an error if a column does not map to a field in the destination.

[go-jet]

No, there can be more destinations then columns, and there can be more columns then destinations.

[josephbuchma]

What do you think about this feature in the context of jet? It's less likely to make a mapping mistake with jet's query builder & generated models, but definitely possible. I've ween bitten by this few times already.

For example, one thing I keep forgetting is that when you embed a struct, you still have to use type name of the embedded struct. Would love to get an error when this happens :)

[go-jet]

Yeah, I agree such a feature would be beneficial. The only concern is will it potentially brake mapping for existing users with more columns then destinations queries. The solution might be to add a new strict query method, or some config for strict mapping, or just make a change and hope that users with bad queries have test coverage over all their queries and CI setup.