Calling stored procedure with ExecuteQuery oddities RRS feed

  • Question

  • I am running into some oddities with calling stored procedures via ExecuteQuery.

    I can call it just fine but when I get the result back, there is some difference between how ExecuteQuery and design-time sproc support handles entity mapping it seems.

    For example, using ExecuteQuery, I can't seem to map the source column to a property of different name by using ColumnAttribute.

    Another thing is I've noticed that Money type in sql can be mapped to double just fine using the design-time sproc call but not through ExecuteQuery.  It insists on receiving it as decimal.

    Are these known issues?



    Thursday, July 15, 2010 8:19 PM

All replies