Why Entity Framework 4 sucks today
-
I beat my head for an hour on this[^] bug today. Microsoft, my employer wants a refund on that hour please - I'll tell you where you can put the check. May not seem like a big thing at first blush, and all in all, I like EF 4. But this small bug has the potential to silently render part of your data useless over time, by overwriting data calculated/updated on the server, with data from the EF objects (mostly default values, like null or 0). I never would have known about it until we had been in production for a while and "mystery problems" started appearing.
-
I beat my head for an hour on this[^] bug today. Microsoft, my employer wants a refund on that hour please - I'll tell you where you can put the check. May not seem like a big thing at first blush, and all in all, I like EF 4. But this small bug has the potential to silently render part of your data useless over time, by overwriting data calculated/updated on the server, with data from the EF objects (mostly default values, like null or 0). I never would have known about it until we had been in production for a while and "mystery problems" started appearing.
-
I beat my head for an hour on this[^] bug today. Microsoft, my employer wants a refund on that hour please - I'll tell you where you can put the check. May not seem like a big thing at first blush, and all in all, I like EF 4. But this small bug has the potential to silently render part of your data useless over time, by overwriting data calculated/updated on the server, with data from the EF objects (mostly default values, like null or 0). I never would have known about it until we had been in production for a while and "mystery problems" started appearing.
Started looking at entity framework today as a matter of fact. I see little value for it since I code alone. I usually start with GUI and work back to the db and then back to GUI in iterations. The entity framework assumes you have a finished db design and are ready to code from it. 2 cents.
-
Started looking at entity framework today as a matter of fact. I see little value for it since I code alone. I usually start with GUI and work back to the db and then back to GUI in iterations. The entity framework assumes you have a finished db design and are ready to code from it. 2 cents.
EF4 would work very well with you. As it lets you start from your C# model classes and generate the DB from it! ;)
A train station is where the train stops. A bus station is where the bus stops. On my desk, I have a work station.... _________________________________________________________ My programs never have bugs, they just develop random features.
-
I beat my head for an hour on this[^] bug today. Microsoft, my employer wants a refund on that hour please - I'll tell you where you can put the check. May not seem like a big thing at first blush, and all in all, I like EF 4. But this small bug has the potential to silently render part of your data useless over time, by overwriting data calculated/updated on the server, with data from the EF objects (mostly default values, like null or 0). I never would have known about it until we had been in production for a while and "mystery problems" started appearing.
Another Wont Fix. I guess VS2012 is gonna be great :)
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
Started looking at entity framework today as a matter of fact. I see little value for it since I code alone. I usually start with GUI and work back to the db and then back to GUI in iterations. The entity framework assumes you have a finished db design and are ready to code from it. 2 cents.
Actually they leave it up to the developers to decide which way they want to do it, so they have to support model->database and database->model. In my researching the bug in the original post, I found that if I had been working model->database, the bug would not have happened. But I am using Migrator.Net to manage schema revisions, and so I have to work database->model instead of the other way round. (Requirements are a bit of a mess so I'm having to build as I go)
-
Another Wont Fix. I guess VS2012 is gonna be great :)
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth EditionAs far as I can tell, the related bug (#505178[^]) has been marked as fixed. They only bit they are saying they aren't going to fix is the request to rename the values. In fairness, I can see why renaming values is a pain as they then have to support multiple sets of syntax for all the people who don't change.
Simon
-
As far as I can tell, the related bug (#505178[^]) has been marked as fixed. They only bit they are saying they aren't going to fix is the request to rename the values. In fairness, I can see why renaming values is a pain as they then have to support multiple sets of syntax for all the people who don't change.
Simon
VS2012 is still gonna great :)
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
VS2012 is still gonna great :)
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth EditionI'm looking forward to Direct Brain Interface Studio 2020
Simon