流利的NHibernate现在准备好生产代码了吗? [英] Is Fluent NHibernate ready for production code now?

查看:480
本文介绍了流利的NHibernate现在准备好生产代码了吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这个问题的主题本身就是有说服力的。我想知道如果流利NHibernate准备生产的代码。我特别想知道一些看似简单的问题,我还没有找到完全令人满意的解决方案(而社区没有解决方案?)。

为什么流利NHibernate忽略我的约定?



是的,我知道这个

现在流利的NHibernate已经可以投入使用了吗?

你测量什么度量生产准备?生产如何比其他环境更严格?只有你可以决定是否满足你的需求。



你有第一个问题的解决方法。流利的NHibernate是开源的,如果人们没有因为bug而死亡(也就是说,有一个可用的工作),那么当有更重要的东西需要处理的时候,我们有限的资源不太可能花在它上面。枚举是一个已知的问题,主要是因为有50%的人期望他们被映射为整数,其他人期望字符串;无论哪种方式,一方会认为执行是一个错误。



第二个问题看起来像一个错误。有趣的是,流利的NHibernate开发人员并没有对堆栈溢出进行拖拽以查找可能的错误。如果你不告诉我们存在一个错误,我们将无法修复它。


$ b 流利的NHibernate已经过去了1.0,这对OSS项目来说是一个重要的里程碑,并且已经被数百个生产应用程序所使用。是否能让它生产就绪只能由你来决定。



如果你觉得它还没有准备好,那它就是开源的,我们一直在寻找给贡献者。


The subject of this question speaks for itself. I am wondering if Fluent NHibernate is ready for production code. I am especially wondering in light of some seemingly simple problems that I am having with it that I haven't yet found fully satisfactory solutions for (and the community doesn't have a solution for?)

Why is Fluent NHibernate ignoring my convention?

Why is Fluent NHibernate ignorning my unique constraint on a component?

Yes, I am aware of this old question which is more than a year old; the answer seems to be kinda-sorta-maybe.

Is Fluent NHibernate is ready for production now?

解决方案

By what metric do you measure "production ready"? How is production any more stringent than other environments? Only you can decide if it meets your needs.

Your first question you have a work around for. Fluent NHibernate is open source, if people aren't dying because of a bug (aka, there's a work around available), it's unlikely our finite resources will be spent on it when there are more important things to be working on. Enums are a known issue, primarily because 50% of people expect them to be mapped as ints, and the others expect strings; either way, one party is going to think that the implementation is a bug.

Your second question looks like a bug. Funnily enough, the Fluent NHibernate developers don't trawl Stack Overflow for possible bugs. If you don't tell us that a bug exists, we won't be able to fix it; sadly, I'm not psychic.

Fluent NHibernate has is past 1.0, which is quite a significant milestone for an OSS project, and is in use in hundreds of production applications. Whether that makes it "production ready" can only be decided by you.

If you don't think it's production ready yet, it's open source and we're always looking for contributors.

这篇关于流利的NHibernate现在准备好生产代码了吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆