It is great that EF has finally acknowledged the problem. Sadly, I have seen multiple instances in the past where they acknowledged a problem and claimed to be working on a fix that either took an inordinate amount of time to fix or the fix never materialized and the functionality was permanently lost. I won't be placing any big bets on them fixing this anytime soon.