MySQL 仍然是免费/开源数据库的不错选择吗？
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/3672367/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Is MySQL still a good choice for a free/open source database?
提问by luiscubal
Until recently, I've used MySQL for all my database needs in all my server projects.
直到最近，我都使用 MySQL 来满足我所有服务器项目中的所有数据库需求。
However, after Oracle came along and bought MySQL, there seems to be some uncertainty about the future of MySQL.
不过，在甲骨文出手收购MySQL之后，MySQL的未来似乎有些不确定。
So I'm left wondering whether I should stick to MySQL (which I'm fairly familiar with), or should I switch to something like PostgreSQL. Any thoughts?
所以我想知道我是否应该坚持使用 MySQL（我非常熟悉），或者我应该切换到像 PostgreSQL 这样的东西。有什么想法吗？
采纳答案by bobince
MySQL and PostgreSQL are both open-source DBMSs that will continue to be developed by independent parties should their current maintainers (corporate or otherwise) get bored. MySQL already has some interesting forks such as Drizzlewhich may rise to more prominence if Oracle choose to let the original project stagnate (well, more than Sun did...).
MySQL 和 PostgreSQL 都是开源 DBMS，如果他们当前的维护者（公司或其他人）感到无聊，它们将继续由独立方开发。MySQL 已经有一些有趣的分支，例如Drizzle，如果 Oracle 选择让原始项目停滞不前，它可能会变得更加突出（嗯，比 Sun 做的更多……）。
You should choose based on your projects' technical needs rather than nebulous arguments that one or the other is going to ‘win'.
您应该根据项目的技术需求进行选择，而不是关于一个或另一个将“获胜”的模棱两可的论点。
(Personally I definitely think it's a good idea to have experience with both.)
（就我个人而言，我绝对认为对两者都有经验是个好主意。）
回答by Seth
If you're looking for a reason to switch to postgres, "Sunoracle bought MySQL" isn't a good one. MySQL is going to be around for a while.
如果您正在寻找切换到 postgres 的理由，“Sunoracle 购买了 MySQL”并不是一个好的选择。MySQL 会存在一段时间。
From Oracle Makes Commitments to ... Users of MySQL:
4.Commitment to enhance MySQL in the future under the GPL. Oracle shall continue to enhance MySQL and make subsequent versions of MySQL, including Version 6, available under the GPL. Oracle will not release any new, enhanced version of MySQL Enterprise Edition without contemporaneously releasing a new, also enhanced version of MySQL Community Edition licensed under the GPL. Oracle shall continue to make the source code of all versions of MySQL Community Edition publicly available at no charge.
...
6. Increase spending on MySQL research and development. Oracle commits to make available appropriate funding for the MySQL continued development (GPL version and commercial version). During each of the next three years, Oracle will spend more on research and development (R&D) for the MySQL Global Business Unit than Sun spent in its most recent fiscal year (USD 24 million) preceding the closing of the transaction.
4.承诺在GPL下未来增强MySQL。Oracle 将继续增强 MySQL，并使 MySQL 的后续版本（包括第 6 版）在 GPL 下可用。Oracle 不会发布任何新的、增强的 MySQL 企业版版本，除非同时发布根据 GPL 许可的 MySQL 社区版的新的增强版本。Oracle 将继续免费公开 MySQL 社区版所有版本的源代码。
...
6、加大MySQL研发投入。Oracle 承诺为 MySQL 的持续开发（GPL 版和商业版）提供适当的资金。在接下来的三年中，甲骨文在 MySQL 全球业务部门的研发 (R&D) 支出将超过 Sun 在交易完成前的最近一个财年（2400 万美元）的支出。
Even with that, remember, it's GPL. If Oracle does something really dumb, the worst-case scenario is a fork.
即便如此，请记住，它是 GPL。如果 Oracle 做了一些非常愚蠢的事情，最坏的情况就是分叉。
回答by Frank Heikens
MySQL was already in trouble before Oracle bought SUN, development of version 6.0 was canceled, just like version 5.4.
在甲骨文收购SUN之前MySQL已经陷入困境，6.0版本的开发被取消，就像5.4版本一样。
Version 5.1 is supported until the end of this year, 2010-12-31, after that, only extended support is available, but you have to pay for it. No more community patches. Version 5.5 or 5.6 are still not GA, still alpha and/or beta. If you can live without patches, just go on, if want patches but don't want the bill, move on to a different database.
5.1 版本支持到今年年底，2010-12-31之后，只有扩展支持可用，但你必须付费。没有更多的社区补丁。5.5 或 5.6 版仍然不是 GA，仍然是 alpha 和/或 beta。如果您可以不用补丁就继续，如果想要补丁但不想要账单，请转到不同的数据库。
MariaDB (Monty's new product) is using the MySQL-code, his last patches came months after MySQL released it's patches. MariaDB doesn't look too good, it wants to stay very close to the original and has it's dependencies. MariaDB might be in trouble next year for it's support on 5.1 versions.
MariaDB（Monty 的新产品）正在使用 MySQL 代码，他的最后一个补丁是在 MySQL 发布补丁几个月后发布的。MariaDB 看起来不太好，它希望非常接近原始版本并具有它的依赖项。MariaDB 明年可能会遇到麻烦，因为它支持 5.1 版本。
And all these problems started before Oracle got involved. Many reasons to move away from MySQL, but (imho) Oracle is't the main problem. Oracle wants money and their customers are going to pay, that has been crystal clear from the start.
所有这些问题都是在 Oracle 介入之前就开始的。远离 MySQL 的原因有很多，但（恕我直言）Oracle 不是主要问题。甲骨文想要钱，而他们的客户会付钱，这一点从一开始就非常清楚。
回答by Abe Miessler
A similar thing happened with Sybase and it seemed like a fairly smooth transition. Of course that's not the same situation, but they are similar...
Sybase 也发生了类似的事情，过渡似乎相当顺利。当然这不是同一种情况，但它们是相似的......
For what it's worth Oracle claims MySQL will be around for a while to come...
Oracle 声称 MySQL 将在未来一段时间内存在，这是值得的……
回答by Marc B
If MySQL's working fine for you right now, then there's no reason to switch, unless you need a feature that's only available in other RDMBSs. As for MySQL's future, even if Oracle were to kill it outright at this very moment, the GPL license ensures that MySQL's source will live on. Might have to be called something else (like MariaDB) due to trademarks, but the program itself can't be killed.
如果 MySQL 现在对您来说工作正常，那么没有理由切换，除非您需要一个仅在其他 RDMBS 中可用的功能。至于 MySQL 的未来，即使 Oracle 在这一刻彻底杀死它，GPL 许可证也确保 MySQL 的源代码将继续存在。由于商标的原因，可能不得不被称为其他东西（如 MariaDB），但程序本身不能被杀死。
回答by Jay
On the one hand, I wouldn't take Oracle's promises to continue to develop MySQL too seriously. Any time a company buys out a product that competes with one of their own, they make statements that they will fully support it indefinately. But often a few years (or months) later they quietly pull the product from the market and provide customers with an "upgrade path" to their own product. Let me hasten to add that I don't claim to have any inside track on Oracle or MySQL. This is just a general observation.
一方面，我不会太认真地对待 Oracle 继续开发 MySQL 的承诺。每当一家公司购买与他们自己的产品竞争的产品时，他们都会声明他们将无限期地全力支持它。但往往几年（或几个月）后，他们悄悄地将产品从市场上撤下，并为客户提供一条“升级路径”到他们自己的产品。让我赶紧补充一点，我并没有声称在 Oracle 或 MySQL 上有任何内部跟踪。这只是一般的观察。
That said, if the current version of MySQL meets your needs, then so what if Oracle never makes any further updates ever? There are plenty of people out there using versions of MySQL that are many years old who have never bothered to upgrade to the current version. I'd say just go ahead and use MySQL. If Oracle's support proves weak or even non-existant, and at some point other database products are adding features that you could really use and that Oracle isn't providing, then you might have a reason to migrate. Sure, there might be compatibility problems. But at this point there are a stack of what-if's: What if Oracle doesn't support the product? What if useful new features are added to other products? What if my code isn't compatible? What if Martians invade? etc
也就是说，如果当前版本的 MySQL 满足您的需求，那么如果 Oracle 永远不会进行任何进一步的更新呢？有很多人在使用多年以前的 MySQL 版本，他们从来没有费心升级到当前版本。我会说继续使用MySQL。如果证明 Oracle 的支持很弱甚至不存在，并且在某些时候其他数据库产品正在添加您可以真正使用而 Oracle 没有提供的功能，那么您可能有理由进行迁移。当然，可能存在兼容性问题。但此时有一堆假设：如果 Oracle 不支持该产品怎么办？如果将有用的新功能添加到其他产品中会怎样？如果我的代码不兼容怎么办？如果火星人入侵怎么办？等等
