Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

60%
+1 −0
Q&A Updating the database reverses previous changes

Disclaimer: I don't work with EF therefore not an expert. EF is tricky and has a lot of dark magic inside so if you're not sure how it all works best to use good old plain SQL or simple libraries....

posted 1y ago by FoggyFinder‭  ·  edited 1y ago by FoggyFinder‭

Answer
#2: Post edited by user avatar FoggyFinder‭ · 2023-04-29T10:44:29Z (over 1 year ago)
  • Disclaimer: I don't work with EF therefore not an expert.
  • EF is tricky and has a lot of dark magic inside so if you're not sure how it all works best to use good old plain SQL or simple libraries.
  • -----
  • I think you see this behaviour because you return old "blog" object, which isn't the same as new "blog" that you wrote to the db.
  • So I suppose your intention was to return "new" `blog` instead, e.g:
  • ```cs
  • static Blog SetupBlog()
  • {
  • using var context = new BloggingContext();
  • var blog = new Blog { Url = "http://blogs.msdn.com/adonet" };
  • blog.Posts.Add(new Post { Title = "Hello World", Content = "I wrote an app using EF Core!" });
  • context.Add(blog);
  • context.SaveChanges();
  • // return blog;
  • return context.Blogs.First();
  • }
  • ```
  • with this change it prints
  • ```
  • Initial posts
  • =============
  • Hello World: I wrote an app using EF Core!
  • After editing
  • =============
  • Hello World (edited): I wrote an app using EF Core!
  • After adding a new post
  • =======================
  • Hello World (edited): I wrote an app using EF Core!
  • Goodbye World: Some content
  • ```
  • -----
  • Hints:
  • 1. You can track state of entities by using [`ChangeTracker`](https://learn.microsoft.com/en-us/ef/core/change-tracking/debug-views)
  • ```csharp
  • context.ChangeTracker.DetectChanges();
  • Console.WriteLine(context.ChangeTracker.DebugView.LongView);
  • ```
  • 2. EF automatically detect changes so you don't have to use "Updates" explicitly
  • Disclaimer: I don't work with EF therefore not an expert.
  • EF is tricky and has a lot of dark magic inside so if you're not sure how it all works best to use good old plain SQL or simple libraries.
  • -----
  • I think you see this behaviour because you return old "blog" object, which isn't the same as new "blog" that you wrote to the db.
  • So I suppose your intention was to return "new" `blog` instead, e.g:
  • ```cs
  • static Blog SetupBlog()
  • {
  • using var context = new BloggingContext();
  • var blog = new Blog { Url = "http://blogs.msdn.com/adonet" };
  • blog.Posts.Add(new Post { Title = "Hello World", Content = "I wrote an app using EF Core!" });
  • context.Add(blog);
  • context.SaveChanges();
  • // return blog;
  • return context.Blogs.First();
  • }
  • ```
  • with this change it prints
  • ```
  • Initial posts
  • =============
  • Hello World: I wrote an app using EF Core!
  • After editing
  • =============
  • Hello World (edited): I wrote an app using EF Core!
  • After adding a new post
  • =======================
  • Hello World (edited): I wrote an app using EF Core!
  • Goodbye World: Some content
  • ```
  • -----
  • Hints:
  • 1. You can track state of entities by using [`ChangeTracker`](https://learn.microsoft.com/en-us/ef/core/change-tracking/debug-views)
  • ```csharp
  • context.ChangeTracker.DetectChanges();
  • Console.WriteLine(context.ChangeTracker.DebugView.LongView);
  • ```
  • 2. EF automatically detects changes so you don't have to use "Updates" explicitly
#1: Initial revision by user avatar FoggyFinder‭ · 2023-04-29T10:43:36Z (over 1 year ago)
Disclaimer: I don't work with EF therefore not an expert.
EF is tricky and has a lot of dark magic inside so if you're not sure how it all works best to use good old plain SQL or simple libraries.

-----

I think you see this behaviour because you return old "blog" object, which isn't the same as new "blog" that you wrote to the db.

So I suppose your intention was to return "new" `blog` instead, e.g:

```cs
    static Blog SetupBlog()
    {
        using var context = new BloggingContext();

        var blog = new Blog { Url = "http://blogs.msdn.com/adonet" };
        blog.Posts.Add(new Post { Title = "Hello World", Content = "I wrote an app using EF Core!" });
        context.Add(blog);
        context.SaveChanges();
        // return blog;
        return context.Blogs.First();
    }
```

with this change it prints

```

Initial posts
=============
Hello World: I wrote an app using EF Core!

After editing
=============
Hello World (edited): I wrote an app using EF Core!

After adding a new post
=======================
Hello World (edited): I wrote an app using EF Core!
Goodbye World: Some content
```
-----

Hints:
1. You can track state of entities by using [`ChangeTracker`](https://learn.microsoft.com/en-us/ef/core/change-tracking/debug-views)

```csharp
context.ChangeTracker.DetectChanges();
Console.WriteLine(context.ChangeTracker.DebugView.LongView);
```
2. EF automatically detect changes so you don't have to use "Updates" explicitly