由 dbml 形成的数据访问层中的功能
我得到了一个由一个 DBML 形成的数据访问层，其中我只包含我需要的所有对象。是否有必要在此 dbml 中编写更多功能，或者我可以仅使用 dbml 作为我的 DAL 吗？我问这个问题是因为我目前正在编写功能，例如从业务逻辑层的表中获取所有文章。所以我现在有点迷失了。可以给出什么样的例子，以便我清楚在业务层中放置什么。
I got a Data Access Layer that's being formed by one DBML in which i just include all object I need. Is it necessary to write more functionality in this dbml or can I just use the dbml as my DAL? I ask this because I am currently writing functionality to, for example, get all Articles from a Table in the Business Logic Layer. So I'm kind of lost now. What kind of examples can be given so that it's clear to me what to put in the Business Layer.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
业务逻辑层基本上是放置业务规则和业务实体的地方。您可以在其中执行诸如有效性检查之类的操作，以确保用户可以添加文章、编辑文章、删除文章等。目的是集中所有业务规则和实体，以便表示层不会需要了解底层的数据库结构，并且数据库结构没有定义接口。
至于您是否需要一个，您需要自己决定。
The Business Logic Layer is where you basically put your business rules and business entities. It is where you want to do things such as validity checks on making sure a user can add an Article, Edit an Article, Delete an Article, etc. The purpose is to centralize all your business rules and entities so that the Presentation Layer does not need to know about the underlining DB structure and that the DB structure is not defining the interface.
As far as if you need one you'll need to decide that for yourself.
http://www.microsoft.com/events/ series/modernsoftdev.aspx?tab=webcasts&id=42420
Microsoft 进行了一系列由 Joe Hummel 主持的关于使用 C# 进行现代软件开发的网络广播。在那里，您将找到有关构建低级数据访问层以及它如何与业务层交互的大量内容。我从这些教训中学到了很多……非常好的东西。
http://www.microsoft.com/events/series/modernsoftdev.aspx?tab=webcasts&id=42420
Microsoft did a series of webcasts conducted by Joe Hummel on Modern Software Devevelopment with C#. There you will find a great deal about constructing a low level data-access layer and how it should interact with the business layer. I learn a lot from those lessons.. really good stuff.