3 ms·
Not trying to bash the work that the EF team has done, but with things like not having enum support, which is something I view as so simple and trivial (even Li
by MichaelGG 16y ago
Not trying to bash the work that the EF team has done, but with things like not having enum support, which is something I view as so simple and trivial (even Linq-to-SQL does it), it makes the entire thing seem not so serious.
- nigelsampson 16y agoAgreed, the lack of enum support drives me nuts. Hell I wrote an ORM in the .Net 1.1 days that had it. Still I'm glad they've released this, more "out of band" releases from Microsoft are a good thing. When frameworks and features aren't tied to Visual Studio releases mean the individual teams can iterate a lot quicker (the MVC and Silverlight teams are good examples).
- vyrotek 16y agoHaha, I was going to try and refrain from making a comment about the Enum support... but glad someone brought it up. I'm constantly haggling my friend on the EF team about this issue. I told him we're not dropping LinqToSql until this is resolved! Apparently there are some serious changes to the core of EF that need to happen to support Enums. My friend tried to explain it to me once and it was one of those whoosh moments.
- xpaulbettsx 16y agoWhile I agree it's pretty glaring, in practice it seems pretty unsafe to use Enums along with persistent storage - as soon as the Intern comes along and adds a new enum value in the middle of the set, that column is now corrupted for all new values.