问题描述
使用EF Core 5.0,引入了多对多关系.我陷入了如何通过我的asp .net api更新它们的问题.
With EF Core 5.0 Many-to-many relations are introduced. I'm getting stucked on how to update them through my asp .net api.
对于一对一和一对多关系,有一个约定,只需在属性名称后添加ID.
For One-to-one and One-to-many relations there is a convention by simply adding the property name followed by ID.
public class Blog
{
public int BlogId { get; set; }
public string Url { get; set; }
public BlogImage BlogImage { get; set; }
}
public class BlogImage
{
public int BlogImageId { get; set; }
public byte[] Image { get; set; }
public string Caption { get; set; }
public int BlogId { get; set; }
public Blog Blog { get; set; }
}
因此适当的POST请求可能看起来像
So a propper POST Request could look like
{
"BlogId": 123,
"Url": "example.com",
"BlogImageID": 42
}
但是我无法确定多对多关系中是否有约定或它的样子
but I could not find out if there is a convention or how it look like for Many-to-many relations
public class Post
{
public int PostId { get; set; }
public string Title { get; set; }
public string Content { get; set; }
public ICollection<Tag> Tags { get; set; }
}
public class Tag
{
public string TagId { get; set; }
public ICollection<Post> Posts { get; set; }
}
是否存在使用EF 5.0将http请求的主体映射到多对多关系的约定?
Is there a convention to map the body of a http request to Many-to-many relations using EF 5.0?
推荐答案
请考虑以下两个具有多对多关系的实体-
Consider the following two entities which are in many-to-many relationship -
public class Post
{
public int Id { get; set; }
public string Title { get; set; }
public ICollection<Tag> Tags { get; set; }
}
public class Tag
{
public int Id { get; set; }
public string Name { get; set; }
public ICollection<Post> Posts { get; set; }
}
在更新 Post
实体中的 Tags
时,在最常见的情况下,会从客户端,请求有效负载将类似于-
When updating the Tags
in a Post
entity, in the most common scenario, a new list of tag Id
s are sent from the client-side, and the request payload will look like -
{
"id": 123,
"title": "An Awesome Post",
"tags": [2, 7, 13]
}
通常,您需要定义一个DTO来表示此请求对象,例如-
Typically, you'd want to define a DTO to represent this request object, like -
public class PostUpdateDTO
{
public int Id { get; set; }
public string Title { get; set; }
public List<int> Tags { get; set; }
}
然后,对于更新操作本身,您可以执行类似-
Then, for the update operation itself, you can do something like -
[HttpPut]
public async Task Put([FromBody]PostUpdateDTO dto)
{
// fetch existing Post including related Tags
var post = await _DbCtx.Posts
.Include(p => p.Tags)
.FirstOrDefaultAsync(p => p.Id == dto.Post.Id);
// remove all Tags from the existing list
post.Tags.Clear();
// add new Tags to the list whose Ids are sent by the client
// but to identify them you need the list of all available tags
var availableTags = await _DbCtx.Tags.ToListAsync();
foreach (var id in dto.Tags)
{
post.Tags.Add(availableTags.First(p => p.Id == id));
}
// modify properties of Post if you need, like -
// post.Title = dto.Title;
await _DbCtx.SaveChangesAsync();
}
如您所见,这需要访问数据库以获取所有可用的 Tag
的列表.如果您不喜欢并想跳过它,可以尝试以下方法-
As you can see, this requires a trip to the database to fetch a list of all available Tag
. If you don't like that and want to skip it, you can try the following approach -
[HttpPut]
public async Task Put([FromBody]PostUpdateDTO dto)
{
// fetch existing Post including related Tags
var post = await _DbCtx.Posts
.Include(p => p.Tags)
.FirstOrDefaultAsync(p => p.Id == dto.Post.Id);
// remove Tags which are in the existing Tag list, but not
// in the new list sent by the client
post.Tags.Where(tag => !dto.Tags.Any(id => id == tag.Id))
.ToList().ForEach(tag => post.Tags.Remove(tag));
// add Tags which are in the new list sent by the client, but
// not in the existing Tag list
dto.Tags.Where(id => !post.Tags.Any(tag => tag.Id == id))
.ToList().ForEach(id => post.Tags.Add(new Tag { Id = id }));
// modify properties of Post if you need, like -
// post.Title = dto.Title;
await _DbCtx.SaveChangesAsync();
}
关于此内容-后跟ID的商品名称:
您要指代的Id属性代表外键.这两个实体都不包含外键属性,因为它们都不依赖于另一个.外键表示父母/孩子或委托人/受抚养人的关系.但是,当两个实体处于多对多关系时,它们彼此独立.
About that - property name followed by ID :
The kind of Id property you are referring to represents a foreign-key. Neither of these two entities contains a foreign-key property, because neither of them depends on the other. A foreign-key implies a parent/child or principal/dependent relationship. But when two entities are in many-to-many relation, they are independent of each other.
这篇关于EF Core 5.0-在ASP.NET Core Web API中更新多对多实体的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!