Mapping rules defined by user
Possibility to define own rules how should be database types mapped to .NET data types.
For example, in Oracle:
Number(1,0) -> (boolean or short)
anonymous
shared this idea
-
Tod Flak
commented
I would also like to see some ability to define column mapping rules. But if you are going to do it, make it flexible!
For my DB, we have many NUMBER(1,0) fields that are in fact boolean, and I like that mapping. But there are a few NUMBER(1,0) fields that actually need to map to short or int. I honestly don't mind manually entering those onto a list somewhere. But I simply hate loosing the ability to do "Update Model from Database.." on my EDMX -- or, still using that functionality, but then having to remember to go "fix" all of the small changes that I have made manully.
What about a list <DoNotAutoUpdate> inside the EDMX.? -
piers7
commented
...and BINARY_FLOAT -> float, not decimal!
-
skippy
commented
boolean
-
sproof
commented
Boolean not the only case. We need:
Number(x,y) -> decimal (for all y>0)