Replies: 1 comment 1 reply
-
I always look for content from Julie Lerman (The Data Farm) when I have EF questions - which is common, as I don't use EF all that often myself 😏 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All,
Im working on a Entity Frame Core CSLA 5.5 prototype project which I am almost done. I haven't done EF in a long time; Its been ADO for the most part but I have done CSLA for a few years now. The only thing left is to get a SQL procedure call working. The issue is that when I pass values from the SqlParameter list any which are null/empty have the value of "default" E.g (@employeeid=default,) on the SQL server. Im not sure if Im doing this correctly. I was thinking maybe there is another class that I should be calling to convert the values into correct DBNull values when passed back to the server. If I change all the "default" values to "null" on the script that is sent to the SQL server it works. Below is code that I am using in the DataAccess.Dal class. By the way if I modify the proc to only take two parameters I and pass values for the two it works fine. Its only when they are empty.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions