shimmy

My feedback

  1. 42 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy commented  · 

    This looks like the optimal solution when using a singleton or long running DbContext.
    However when working with short-lived contexts for example in ASP.NET apps, transactions is another good way to achieve this.

  2. 28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy supported this idea  · 
    shimmy commented  · 

    I read this post and I'm so frustrated it didn't make it into 4.2.
    Very disapointing indeed! Meanwhile here is a great workaround: http://dotnetspeak.com/index.php/2011/03/custom-conventions-in-entity-framework-code-first-v-4-1/

  3. 201 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy supported this idea  · 
  4. 369 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy supported this idea  · 
  5. 486 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy supported this idea  · 
  6. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    shimmy shared this idea  · 
  7. 94 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy commented  · 

    Meanwhile checkout this post: http://goo.gl/5vkQM

    shimmy commented  · 

    @Ladislav, I strongly disagree with you.
    I think this is very compelling and even obvious.
    Class designer doesn't target the features EF has to provide (Key? MaxValue, FixedValue etc.), nor doesn't it target relationships in such an easy way as the EF designer does.
    Besides, "limitation" is why we have partial classes, all the rest the designer doesn't target, is implemented in the partial classes. This is clear as the sun.

  8. 5 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    shimmy shared this idea  · 
  10. 9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy supported this idea  · 
    shimmy commented  · 

    Also should be able to select using a method, there should be a runtime-method cache when generating SQL syntax, so I should be able to use
    context.Unicorns.Select(u=>UnicornFactory.Create(u.Id, u.Myths)), the factory is supposed to return an unknown type based on the parameters.
    This has to be a two-parts query so the details of the SQL are extracted and sent to storage, then using the construction details.

    shimmy shared this idea  · 
  11. 267 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

  12. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    shimmy commented  · 

    I added this by mistake, I mixed this forum with the EF forum, feature already posted there, please vote: http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1083577-objectcontext-discardchanges

    shimmy shared this idea  · 
  13. 34 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy commented  · 

    NOTE: And vice versa when using code-first.
    These features should be on demand.

    shimmy commented  · 

    @Femi A, I agree.
    So this feature should be on demand, so the user can enable it on first generation and then disable it.

    shimmy shared this idea  · 
  14. 8 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy commented  · 

    @Tamus, I believe you're right. It shouldn't inherit from CancelEventArgs.
    This will lead to inconsistency having the user cancel the property-set without notifying the caller.
    BUT, but, but what really really important is, that the candidate value should be provided at the OnPropertyChanging event, then will throw an exception instead of cance, which makes more sense.

    *SO FOR CONCLUSION*:
    My original post should be edited and be:
    "Provide the candidate value at the OnPropertyChanging method and in the PropertyChangingEventArgs"
    - so user knows the what the candidate value is, otherwise, the PropertyChanging event makes no sense (getting the candidate value is a tough job and is very performance-expensive).

    Please see this connection:
    https://connect.microsoft.com/VisualStudio/feedback/details/632384/propertychangingeventargs-class-should-provide-the-candidate-value

    shimmy shared this idea  · 
  15. 13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy shared this idea  · 
  16. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy commented  · 

    I know that this is implemented in the context, but I think this event should be raised in each particular entity as well.

    shimmy shared this idea  · 
  17. 9 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    shimmy shared this idea  · 
  18. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)

Feedback and Knowledge Base