I don't know if this is known, but I figured I would post this to let people know, or get info on why this works this way:
I have a DB that defines it's keys as CHAR(15) - Fix length strings. I created a SP with CHAR parms, imported the proc and mapped it to a EF Function.
I ran the code and watched the execution in SQL profiler/QA.
For some reason EF padded the CHAR(15) strings with endless empty strings. I didn't count them, but I am guessing it defined it as CHAR(8000). Only when I defined them as VARCHAR did it run properly in QA.
Is this a known issue with EF?
EWild