Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDataReader Exception. #1

Closed
jbogard opened this issue Dec 29, 2014 · 3 comments
Closed

IDataReader Exception. #1

jbogard opened this issue Dec 29, 2014 · 3 comments

Comments

@jbogard
Copy link
Member

jbogard commented Dec 29, 2014

From @elranu on January 10, 2014 17:7

Hi,
Im getting the following AutoMapperMappingException. Mapping a Reader to an Entity.How I can know which is the column is generating this error?

Mapping types:
IDataReader -> UserEntity
System.Data.IDataReader -> AMSDLL.Entities.UserEntity

Destination path:
UserEntity

Source value:
System.Data.SqlClient.SqlDataReader

Thanks and Regards!

Copied from original issue: AutoMapper/AutoMapper#441

@jbogard
Copy link
Member Author

jbogard commented Dec 29, 2014

From @elranu on January 10, 2014 17:22

Also is there any way to know which row is making the exception?

Thanks!

@jbogard
Copy link
Member Author

jbogard commented Dec 29, 2014

Unfortunately there isn't a way. The mapping is generated as IL. Is there
an inner exception?

On Fri, Jan 10, 2014 at 11:07 AM, Mariano Julio Vicario <
notifications@github.com> wrote:

Hi,
Im getting the following AutoMapperMappingException. Mapping a Reader to
an Entity.How I can know which is the column is generating this error?

Mapping types:
IDataReader -> AMSUserEntity
System.Data.IDataReader -> AMSDLL.Entities.UserEntity

Destination path:
UserEntity

Source value:
System.Data.SqlClient.SqlDataReader

Regards


Reply to this email directly or view it on GitHubhttps://github.com/AutoMapper/AutoMapper/issues/441
.

@jumas45
Copy link

jumas45 commented Oct 4, 2015

You can try removing the columns or adding the columns one by one to find out which is the offending one. It's not ideal but you will figure out eventually.

@jbogard jbogard closed this as completed Nov 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants