I just found some articles that explain how to change the mapping for tables so I imagine columns are just around the corner.
When I say timestamp I mean a unix timestamp which can easily be converted to date AND/OR time - not sure what MSDN is getting at?!?
In the database I wish to store the date "10/10/2013" as 1381381200 but convert to a human friendly date within the PONO.
My entity objects are high level abstractions but I still prefer to store the time in a numeric format - how does EF solve/address this type mis-match? This is/was the impetus behind OR/M frameworks ain't it?