blocks|key|2859060|text|为了所有神圣的东西(以及妇女和儿童)的爱，尽一切可能说服他们不要使用定制的O/RM解决方案。当已经存在完美的开源车轮时，为什么人们还想重新发明车轮？！？！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2859061|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|$]]

For the love of all that's holy (and the women and the children), do everything possible to convince them not to go with a custom O/RM solution. Why are people wanting to re-invent the wheel when there are perfectly-good, open-source wheels already in existence?!?!

blocks|key|543094|text|在我看来，编写自己的OR/M是你可能做出的最糟糕的设计决策之一。“可维护性和灵活性”正是不编写自己的OR/M的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|543095|请阅读See+25+Reasons+Not+To+Write+Your+Own+Object+Relational+Mapper，看看你的客户是否真的愿意支付建造NHibernate+(760万美元)或SubSonic+(150万美元)之类的东西的成本。因为，就像ChanChan上面说的，你最终会得到类似的结果。|offset|length|543096|entityMap|0|LINK|mutability|MUTABLE|url|http://ayende.com/Blog/archive/2006/05/12/25ReasonsNotToWriteYourOwnObjectRelationalMapper.aspx|1|http://www.ohloh.net/projects/nhibernate|2|http://www.ohloh.net/projects/6727^0|0|3|1P|0|29|A|1|2T|8|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]|$D|W|E|X|1|Y]|$D|Z|E|10|1|11]]|A|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]|P|$5|I|J|K|A|$L|Q]]]]

IMO writing your own OR/M is one the worst design decisions you could ever make. "maintainability and flexibility" are reasons exactly NOT to write your own OR/M.

Please read <a href="http://ayende.com/Blog/archive/2006/05/12/25ReasonsNotToWriteYourOwnObjectRelationalMapper.aspx" rel="nofollow noreferrer">See 25 Reasons Not To Write Your Own Object Relational Mapper</a>, and see if your client really wants to pay what it costs to build something like <a href="http://www.ohloh.net/projects/nhibernate" rel="nofollow noreferrer">NHibernate</a> ($7.6M) or <a href="http://www.ohloh.net/projects/6727" rel="nofollow noreferrer">SubSonic</a> ($1.5M). Because, like ChanChan said above, you will end up with something similar to that.

blocks|key|4326216|text|有一大堆来自Davy+Brion+(+NHibernate提交者)的帖子，出于某种原因，他也被迫为客户编写定制的ORM。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4326217|他谈到的一些事情包括：|4326218|开箱即用CRUD+Functionality|4326219|Hydrating+Entities|unordered-list-item|4326220|
|4326221|Session+Level+Cache|4326222|4326223|Executing自定义查询|4326224|映射类到表|4326225|4326226|4326227|4326228|如果你一定要走这条路，绝对值得一试：Build+Your+Own+Data+Access+Layer+Series|offset|length|4326229|entityMap|0|LINK|mutability|MUTABLE|url|http://davybrion.com/blog/2009/08/build-your-own-data-access-layer-series/^0|0|0|0|0|0|0|0|0|0|0|0|0|I|13|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|1B|8|@]|9|@]|A|$]]|$1|M|3|J|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|H|7|1D|8|@]|9|@]|A|$]]|$1|P|3|Q|5|H|7|1E|8|@]|9|@]|A|$]]|$1|R|3|-4|5|H|7|1F|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1I|8|@]|9|@$W|1J|X|1K|1|1L]]|A|$]]|$1|Y|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

There's a bunch of posts by Davy Brion (an NHibernate committer) who is for some reason also forced to write a custom ORM for a client.

Some of the things he covers are:

<ul>
<li>Mapping Classes To Tables</li>
<li>Out Of The Box CRUD Functionality</li>
<li>Hydrating Entities</li>
<li>Session Level Cache</li>
<li>Executing Custom Queries</li>
</ul>

Definately worth checking out, if you MUST go down this path: <a href="http://davybrion.com/blog/2009/08/build-your-own-data-access-layer-series/" rel="nofollow noreferrer">Build Your Own Data Access Layer Series</a>

blocks|key|2859023|text|在我的经验中，你需要使用nHibernate风格，这样你就可以在你的对象和数据库之间建立某种映射。这允许您的对象具有一些在数据库中难以表示但在POCOs中更容易表示的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2859024|生成使您可以通过提供满足您的模式的类来开始，但是如果您计划维护或测试任何东西，那么映射现在是痛苦的，以后会带来乐趣。|2859025|Subsonic是一个很棒的模型，它的开源，如果你一定要去生成，可以在myGeneration中使用他们的模板来获得帮助。|2859026|BTW:我已经做了你正在做的事情，我最终得到了非常类似于亚音速的东西，现在我建议我的客户拿着亚音源，为自己分叉它。|offset|length|style|BOLD|2859027|entityMap^0|0|0|0|0|1L|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@$H|R|I|S|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

You need to go the nHibernate style, in my experience, and have it so that you have some kind of map, between your objects and the database. This allows your objects to have some things that are hard to represent in a database but are easier represented in POCOs.

Generation gets you started, by giving you classes that meet your schema, but if you plan on maintaining anything or testing anything, mapping is pain now for pleasure later.

Subsonic is a great model, and its open source, if you must go generation, use their templates in myGeneration to get a leg up.

BTW: I've done what you are doing, and I ended up with something very similar to subsonic, and now advise my clients to take the subsonic source, and fork it for themselves.

blocks|key|2859159|text|也许只是可能，你迫切需要一些在现有解决方案中还不存在的“功能”。也许你也需要一些更简单的东西。1.5美元的亚音速简直太离谱了。也许你想用POCO。也许你想在3层场景中轻松地使用这些东西。也许你不想支持这个星球上的所有RDBMS，所以你可以针对你的目标对代码进行硬编码和优化。也许你想实现更智能的对象跟踪。也许现有的orms所做的一些设计决定会让你发疯……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2859160|我自己使用的是我自己和我自己开发的定制orm，我很满意我这样做了。地毯下没有隐藏的龙，没有令人惊讶的场景。我的orm做了我想要它做的事情，不会少，也不会更多。|2859161|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Maybe just maybe, you need badly some "features" that do not exist yet in the existing solutions. Maybe you need something simpler also. 1.5$ for Subsonic is simply outrageous. 
Maybe you want to use POCO. Maybe you want to use the stuff easily in a 3 tier scenario.
Maybe you don't want to support ALL RDBMS on the planet, so you can hardcode and optimize the code just for your target. Maybe you want to implement smarter object tracking. Maybe some design decisions made by the existing orms drive you crazy....

I myself am using a custom orm developed by me myself and i, and i am satisfied that i did it. There is no hidden dragon under the carpet, no surprise scenario. My orm does exacty what i want it to do, nothing less, nothing more.

blocks|key|4326329|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4326330|二级缓存|unordered-list-item|4326331|4326332|允许您在内存中维护实体实例|4326333|-+Automatic+dirty-checking|code-block|syntax|javascript|4326334|允许您在不加载对象的情况下更新对象中的更改。|4326335|-强大的查询语言|4326336|-强大的级联操作|4326337|-强大的主键生成器策略|4326338|ORM框架将根据目标数据库选择最佳的主键生成器策略|4326339|-支持复合元素|4326340|-支持事件|4326341|onSave、onUpdate等|4326342|-好的文档和参考书|4326343|-支持会话状态|4326344|​|4326345|致以敬意，|4326346|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|1B|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|1C|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|1E|7|@]|8|@]|9|$]]|$1|G|3|H|4|I|6|1F|7|@]|8|@]|9|$J|K]]|$1|L|3|M|4|5|6|1G|7|@]|8|@]|9|$]]|$1|N|3|O|4|5|6|1H|7|@]|8|@]|9|$]]|$1|P|3|Q|4|5|6|1I|7|@]|8|@]|9|$]]|$1|R|3|S|4|5|6|1J|7|@]|8|@]|9|$]]|$1|T|3|U|4|5|6|1K|7|@]|8|@]|9|$]]|$1|V|3|W|4|5|6|1L|7|@]|8|@]|9|$]]|$1|X|3|Y|4|5|6|1M|7|@]|8|@]|9|$]]|$1|Z|3|10|4|5|6|1N|7|@]|8|@]|9|$]]|$1|11|3|12|4|5|6|1O|7|@]|8|@]|9|$]]|$1|13|3|14|4|5|6|1P|7|@]|8|@]|9|$]]|$1|15|3|16|4|5|6|1Q|7|@]|8|@]|9|$]]|$1|17|3|18|4|5|6|1R|7|@]|8|@]|9|$]]|$1|19|3|-4|4|5|6|1S|7|@]|8|@]|9|$]]]|1A|$]]

<ul>
<li>Second level cache

Allows you maintain entities instances in-memory

<ul>
<li>Automatic dirty-checking

Allows you updates changes in an object without loading it.</li>
<li>Powerful query language</li>
<li>Powerful cascade operation</li>
<li>Powerful primary key generator strategy

ORM framework will pickup best primary key generator strategy according to target database </li>
<li>Support to composite elements</li>
<li>Support to events

onSave, onUpdate and so on</li>
<li>Good documentation and reference books</li>
<li>Support to conversational state</li>
</ul></li>
</ul>

regards,

blocks|key|543222|text|目前还没有人提到这一点；但请使用LLBLGen。您可以根据自己的喜好自定义模板，显然，您也可以在生成的类中编写自己的自定义代码。买下它。你永远不会回头看，你会说：“谢谢你，西尔基！”当它一直工作得很好时。(它不是我写的，但我喜欢它)。如果它对你不起作用，你也可以说“去你的丝绸！”但这不太可能，尽管我确实提供了它作为一个选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|543223|我注意到LLBLGen唯一不好的地方就是支持在数据库/服务器之间进行动态切换。它不支持我想要的特性；即检测您检索到的给定实体在您切换到的新数据库中不“存在”的能力。但这是一种罕见的情况。|543224|我建议使用LLBLGen，因为当我遇到它时，我正在编写自己的OR/M。再也不回头了。|543225|entityMap|0|LINK|mutability|MUTABLE|url|http://www.llblgen.com/^0|G|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

No-one has mentioned it yet; but go with <a href="http://www.llblgen.com/" rel="nofollow noreferrer">LLBLGen</a>. You may customise the template as you like, and you may also, obviously, write your own custom code in the generated classes. Buy it. You will never look back, and you will be saying "Thank you silky!" when it consistently works beautifully. (I didn't write it, but I love it). If it doesn't work out for you, you may also say "Damn you silky!". But that's unlikely, however I do offer it as an option.

The only bad thing I noticed about LLBLGen has been the support for switching between Databases/servers on the fly. It doesn't support a feature that I'd like; namely the ability to detect that a given entity you retrieved doesn't "exist" in a new database that you've switched to. But this is a rare case.

I suggest LLBLGen, because I was in the process of writing my own OR/M when I came across it. Never looked back.

blocks|key|2859359|text|作为一名顾问(听起来你就是这样)，你的工作就是利用你的专业知识，以最小的成本和时间投资，为你的客户实现一个满足他们需求的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2859360|如果他们想建造和销售一个运营部，那就进城去做一个。如果他们需要其他东西，可以使用已经存在的工具来完成工作。|2859361|如果他们坚持花钱，买一个现有的(我不会说出任何一个，但有一些好的不是免费的)。|2859362|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|$]]

Your job as a consultant (sounds like that's what you are) is to leverage your expertise in implementing for your clients a solution that fits their desires with a minimum cost and time investment.

If they want to build and sell an OR/M. The go to town making one. If they want anything else, use one that already exists to get the job done.

If they insist on spending money, buy an existing one (I won't name any, but there exist some good ones that are not free).

blocks|key|543351|text|尝试使用Devart+LinqConnect+-+LINQ+to+SQL的所有功能以及对最流行的数据库服务器--+Oracle、MySQL、Postgre、SQL+Server和SQLite的广泛支持。令人难以置信的可视化建模工具，先进的监控工具，高质量的支持-因此，我在项目执行过程中只用了三周就学会了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|543352|entityMap|0|LINK|mutability|MUTABLE|url|http://www.devart.com/linqconnect/^0|4|I|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]]]]

Try to use <a href="http://www.devart.com/linqconnect/" rel="nofollow">Devart LinqConnect</a> - all of the LINQ to SQL features and wide support of the most popular database servers - Oracle, MySQL, Postgre, SQL Server, and SQLite. Incredible Visual Modeling tool, advanced monitoring tool, high quality support - as a result i've learned it only in three weeks during my project execution.

I'm currently working on putting together a fairly simple ORM tool to serve as a framework for various web projects for a client. Most of the projects are internal and will not require massive amounts of concurrency and all will go against SQL Server. I've suggested that they go with ORM tools like SubSonic, NHibernate, and a number of other open source projects out there, but for maintainability and flexibility reasons they want to create something custom. So my question is this: What are some features that I should make sure to include in this ORM tool? BTW, I'll be using MyGeneration to do the code generation templates.

Good Features for an ORM

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我目前正致力于将一个相当简单的ORM工具组合在一起，作为客户各种web项目的框架。大多数项目都是内部项目，不需要大量的并发，所有项目都将与SQL Server背道而驰。我建议他们使用对象关系管理工具，如SubSonic、NHibernate和许多其他开源项目，但出于可维护性和灵活性的原因，他们想要创建一些定制的东西。所以我的问题是:我应该确保在这个ORM工具中包含哪些特性？顺便说一句，我将使用My

问ORM的好特性
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ORM的好特性EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ORM的好特性
EN