blocks|key|2005735|text|MySQL和PostgreSQL都是开源DBMS，如果他们当前的维护者(公司或其他)感到无聊，这些DBMS将由独立的各方继续开发。MySQL已经有一些有趣的分支，比如Drizzle，如果甲骨文选择让原始项目停滞不前(好吧，比Sun...)，它可能会变得更加突出。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2005736|你应该根据你的项目的技术需求来选择，而不是模糊地认为其中一个会“赢”。|2005737|(就我个人而言，我绝对认为两者都有经验是个好主意。)|2005738|entityMap|0|LINK|mutability|MUTABLE|url|http://drizzle.org/^0|2B|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]]]]

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 <a href="http://drizzle.org/" rel="noreferrer">Drizzle</a> which may rise to more prominence if Oracle choose to let the original project stagnate (well, more than Sun did...).

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.)

blocks|key|2005759|text|如果MySQL现在可以很好地为您工作，那么就没有理由切换，除非您需要一个仅在其他RDMBSs中可用的特性。至于MySQL的未来，即使Oracle在这一时刻将其彻底扼杀，GPL许可证也确保了MySQL的源代码将继续存在。由于商标的原因，可能不得不使用其他名称(如MariaDB)，但程序本身不能被终止。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2005760|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|$]]

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.

blocks|key|2005793|text|一方面，我不会把甲骨文继续开发MySQL的承诺看得太重。任何时候，当一家公司买断一个与他们自己竞争的产品时，他们都会发表声明，表示他们将无限期地完全支持它。但通常在几年(或几个月)后，他们会悄悄地将产品从市场上撤出，并为客户提供一条自己产品的“升级路径”。让我赶紧补充一句，我并没有声称有任何关于甲骨文或MySQL的内幕消息。这只是一个普遍的观察结果。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2005794|也就是说，如果当前版本的MySQL满足了您的需求，那么如果Oracle再也不做任何更新又会怎么样呢？有很多人在使用已经有很多年历史的MySQL版本，他们从来没有费心升级到当前的版本。我想说的是继续使用MySQL。如果事实证明Oracle的支持很弱，甚至根本不存在，并且在某个时候，其他数据库产品正在添加您真正需要但Oracle没有提供的特性，那么您可能有理由进行迁移。当然，可能会有兼容性问题。但在这一点上，有一堆假设:如果Oracle不支持该产品怎么办？如果在其他产品中添加了有用的新功能，该怎么办？如果我的代码不兼容怎么办？如果火星人入侵怎么办？等|2005795|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|$]]

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.

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

blocks|key|2005806|text|在甲骨文收购SUN之前，MySQL就已经陷入困境，6.0版的开发被取消，就像5.4版一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2005807|5.1版本支持到今年年底，2010-12-31，在那之后，只有扩展支持可用，但你必须付费。没有更多的社区补丁。5.5或5.6版本仍然不是GA，仍然是alpha和/或beta。如果你可以不打补丁，那就继续吧；如果你想要打补丁，但又不想要账单，那就换个不同的数据库吧。|offset|length|2005808|MariaDB+(蒙蒂的新产品)正在使用MySQL代码，他的最后一个补丁是在MySQL发布补丁几个月后发布的。MariaDB看起来不太好，它想保持与原始版本非常接近，并且有它的依赖项。MariaDB明年可能会遇到麻烦，因为它对5.1版本的支持。|2005809|所有这些问题都是在甲骨文介入之前就开始了。离开MySQL有很多理由，但甲骨文不是主要问题。甲骨文想要钱，他们的客户会付钱，这一点从一开始就非常清楚。|2005810|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mysql.com/about/legal/lifecycle/#calendar^0|0|D|A|0|0|0|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]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

MySQL was already in trouble before Oracle bought SUN, development of version 6.0 was canceled, just like version 5.4.

Version 5.1 is supported until the end of this year, <a href="http://www.mysql.com/about/legal/lifecycle/#calendar" rel="nofollow noreferrer">2010-12-31</a>, 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.

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.

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.

Until recently, I've used MySQL for all my database needs in all my server projects.

However, after Oracle came along and bought MySQL, there seems to be some uncertainty about the future of 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?

Is MySQL still a good choice for a free/open source database?

PostgreSQL

数据库

服务器

MariaDB

MySQL

直到最近，我一直使用MySQL来满足我所有服务器项目中的所有数据库需求。然而，在甲骨文出现并收购MySQL之后，MySQL的未来似乎存在一些不确定性。所以我想知道我是应该坚持使用MySQL (我对它相当熟悉)，还是应该切换到像PostgreSQL这样的东西。有什么想法吗？

问对于免费/开源数据库，MySQL仍然是一个很好的选择吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于免费/开源数据库，MySQL仍然是一个很好的选择吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于免费/开源数据库，MySQL仍然是一个很好的选择吗？
EN