blocks|key|2658576|text|我们用它来保存两个.dbml文件的方法。其中一个持有存储的Procs，所有的生产数据库访问都是通过它完成的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2658577|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The approach that we've used it to keep 2 .dbml files. One of them holds the Stored Procs and all production DB access is done through this. The other is in a unit test folder and holds tables and their relationships and is used for DB data manipulation and querying for unit tests.

blocks|key|2650337|text|超过一定大小后，使用xml而不是dbml设计器可能会变得更容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2650338|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Past a certain size it probably becomes easier to work with the xml instead of the dbml designer.

blocks|key|4070646|text|利用名称空间设置。您可以通过在ORM的空白区域中单击，在属性中找到它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4070647|这允许我为一组业务规则创建一个用户表和一个用户类，并为另一组业务规则创建第二个(但相同的数据存储)用户表和用户类。|4070648|或者，拆分库，这也应该具有根据公司的命名约定更改名称空间的效果。我从来没有开发过需要访问每个表的企业应用程序。|4070649|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Take advantage of the namespace settings. You can get to it in properties from clicking in the white space of the ORM.

This allows me to have a Users table and a User class for one set of business rules and a second (but the same data store) Users table and a User class for another set of business rules.

Or, break up the library, which should also have the affect of changing the namespacing depending on your company's naming conventions. I've never worked on an enterprise app where I needed access to every single table.

blocks|key|289999|text|我已经写了一个实用程序来解决这个问题，我需要一个快速的应用程序来让你只选择你需要的数据库对象。在我的例子中，我经常需要一个复杂的视图，但不需要表。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|290000|http://www.codeplex.com/SqlMetalInclude/|offset|length|290001|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|14|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

I have written a utility to address exactly that problem, I needed a quick app to let you select only the database objects you need. In my case I often needed a complex view, but no tables.

<a href="http://www.codeplex.com/SqlMetalInclude/" rel="nofollow noreferrer">http://www.codeplex.com/SqlMetalInclude/</a>

blocks|key|290003|text|我也写了一个工具！我的是使用c#编写对dbml文件的脚本更改，这样您就可以重新运行它们，而不会丢失更改。查看我的博客http://www.adverseconditionals.com+4更多详细信息|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|290004|entityMap|0|LINK|mutability|MUTABLE|url|http://www.adverseconditionals.com/^0|1M|Y|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I have written a tool too! Mine is for scripting changes to dbml files using c# so you can rerun them and not lose changes. See my blog <a href="http://www.adverseconditionals.com" rel="nofollow noreferrer">http://www.adverseconditionals.com</a> 4 more details

This question is addressed to a degree in this question on <a href="https://stackoverflow.com/questions/33664/best-practices-for-managing-linq-to-sql-dbml-files">LINQ to SQL .dbml best practices</a>, but I am not sure how to add to a question.

One of our applications uses LINQ to SQL and we have currently have one .dbml file for the entire database which is becoming difficult to manage. We are looking at refactoring it a bit into separate files that are more module/functionality specific, but one problem is that many of the high level classes would have to be duplicated in several .dbml files as the associations can't be used across .dbml files (as far as I know), with the additional partial class code as well.

Has anyone grappled with this problem and what recommendations would you make?

Managing LINQ to SQL .dbml model complexity

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

这个问题在上的这个问题中得到了一定程度的解决，但我不确定如何添加到问题中。我们的一个应用程序使用LINQ to SQL，我们目前有一个用于整个数据库的.dbml文件，这变得难以管理。我们正在考虑将其重构到更特定于模块/功能的单独文件中，但一个问题是，许多高级类必须在几个.dbml文件中复制，因为关联不能跨.dbml文件...

问管理LINQ to SQL .dbml模型复杂性
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问管理LINQ to SQL .dbml模型复杂性EN