6 ms·
This is an excellent opportunity for the Postgres community to step up an promote Postgres.
by jedberg 14y ago
This is an excellent opportunity for the Postgres community to step up an promote Postgres.
- rbanffy 14y agoI think this would be a mistake. This is an excellent opportunity to demonstrate that anyone can fork the MySQL codebase and create other plug-in replacement databases with it, such as MariaDB and Drizzle. All that is lost is the MySQL name and brand. PostgreSQL users and developers must seize the opportunity to show businesses that free software cannot be killed, not even by mighty Oracle. They and, most notably, Microsoft, have been trying to kill it for more than a decade now. Because the anti-free-software FUD machine (fed in part by Oracle itself) is already having a wonderful time with this.
- Udo 14y agoI wish I could mod this up a hundred times. PostgreSQL people themselves have been playing into the hands of corporate FUDders with their incessant and inappropriate peddling. MySQL is not your enemy, MS SQL Server is. Oracle's software empire as a whole certainly is your enemy. Show some solidarity with a fellow open source project! MySQL and PostgreSQL represent two very different implementation philosophies, and being able to choose between them according to taste and merits is a good thing. Most of us have suspected that the MySQL project itself was going to die as it was acquired by Oracle, in the same way Open Office died when it was acquired by Oracle. This is a company where good software goes to expire, either due to a deliberate intention or gross incompetence I can't say but I suspect it's a mixture of both. However sad that may be for the MySQL (or OpenOffice) brand name, the code itself lives on and continues to evolve within a rich open source ecosystem. Hence, sensational and petulant "RIP $PRODUCTNAME" articles are unnecessary. There is no threat to existing projects based on MySQL or any other successful open source project for that matter. Not only will this stuff be free forever, it will also continue to grow and be developed on its own. The corporate assassination of open source projects will only work if we let it, it's a purely psychological game.
- jeffdavis 14y agoBackground: I am a postgresql user and developer. I started with MySQL around '99, used both for a while, and then gave up on mysql and haven't really used it since 2007. I do agree that injecting postgresql into every discussion without adding anything new is getting excessive. And declaring mysql dead is clearly premature. But let me respond to this particular point: "Show some solidarity with a fellow open source project!" I guess I never really saw MySQL as an open project. * when I first started using mysql it was not under the GPL, it was under some free-for-non-commercial use license * They pretty much reject the standards completely (introducing nonstandard things like backticks that make migration away from mysql harder for no apparent benefit) * mysql never fostered an outside developer community (by which I mean people developing mysql itself) * the code is messy and poorly structured * the development ecosystem, like revision control and documentation (and now tests) don't seem to be open * the licensing of the client library is restrictive * they require copyright assignment (although not all of the forks do) I hope one of the forks does manage to foster a more open community, but communities aren't built overnight nor are they transplanted easily.
- Udo 14y agoYou might not have seen MySQL as an open project, but I guess we can agree based on the outcome that it turned out to be one? If it hadn't been, open forks would not have been able to form. Of course when you're talking about community, every project seems to have a different atmosphere. Linus Torvalds is famous for not accepting patches or contributions to the Linux kernel, so is that project really open? From the perspective of a developer using MySQL, the community has always been massive, diverse, and helpful. Maybe it was a different experience on the dev mailing list, I wouldn't know. But I do know that in the end, MySQL was open where it really mattered. I can understand though that it was probably easier and more rewarding for an outside developer to get into the inner circles of Postgres than it was to essentially join MySQL AB back in the time when they still existed. > I hope one of the forks does manage to foster a more open community, but communities aren't built overnight nor are they transplanted easily. I assume you're talking about the actual engine development community, and I'm not certain that's really how a lot of open source projects actually work. It seems in most cases you simply have a core group of developers doing their thing, with occasional discussions and input from the outside. I might be wrong, but that's certainly my perception. The Postgres dev community might be different, again I wouldn't know. As an app developer, I have different expectations about that. I'm not going to take part in any discussions about implementation details, nor am I likely to submit any patches. What I care about is software quality and proper documentation, those are not necessarily a function of community.
- jeffdavis 14y ago"All that is lost is the MySQL name and brand." I respectfully disagree. Building a community of database developers is no small task. PostgreSQL has spent a long time fostering a diverse group of developers, maintaining a clean codebase and infrastructure, and having explicit policies and procedures in place that make it easier for new developers to get started. That has never been true for MySQL. Development happens largely because of the money that MySQL AB, then Sun, and now Oracle is paying. Monty is trying to change that with MariaDB (I don't know as much about the others) and I respect that and I hope he succeeds. But it takes a while to go from corporate development to community development successfully -- it doesn't happen overnight, especially in a field like databases where it can be hard to find developers regardless of money.
- rbanffy 14y agoI agree with you. MySQL lost a ton of momentum because of Oracle but given what Oracle is doing with the original MySQL, I suspect keeping up with it does not require as much effort as it did getting to where it is now. If MySQL forks get the developer attention they need, and set themselves up in a way they can share code between themselves and, maybe, with PostgreSQL, it will continue evolving. Having one single corporate sponsor is always a very bad idea for open-source projects. I hope MySQL derivatives have learned this lesson. And, I imagine, the dual-licensing thing has to go. That's no longer a viable way to sustain development.
- jeffdavis 14y ago"MySQL lost a ton of momentum because of Oracle" Aside: why, oh why, did 3 mysql forks appear when MySQL AB was bought? Couldn't they coalesce around one alternative? Ordinarily, I'm not against a little healthy competition. I think forks and trying new ideas is great. But the timing just makes no sense to me from any rational point of view. "I suspect keeping up with it does not require as much effort as it did getting to where it is now... maybe... it will continue evolving." True, but I'd hate to see the bar set that low.
- rbanffy 14y ago
- taligent 14y agoI don't think that's a problem. As we've seen for years PostgreSQL users will quite happily and naturally remind everyone how much superior it is to MySQL (and every other database) at every opportunity.
- einhverfr 14y agoI don't think that's the case. I haven't heard PostgreSQL users trash Firebird or SQLite. The complaints about MySQL are rather specific and have historical roots regarding MySQL saying things like: * you don't need transactions * you don't need foreign key constraints * you don't need ACID-compliance At least the NoSQL folks tend to be honest about their products not replacing the traditional RDBMS approach.... Granted many of these don't apply anymore, but then legacies live on interaction-wise. This being said, I know very few real Pg users who harp on MySQL anymore. Most of us figure that Oracle does better advocacy on this area than we can.
- its_so_on 14y agolol @ "At least the NoSQL folks tend to be HONEST about their products not replacing the traditional RDBMS approach...." More like, technically true, but contrary to the whole reason for doing what they're doing. Nobody puts a lot of work into something "honestly" not intending to replace the thing it's replacing. They say this to appease the people who point out that it doesn't do all the same things. If I built a better alternative to a common item, you could bet your bottom dollar i would be very "honest" about it not replacing that common item. The last thing that statement would be is "honest." It's appeasement.
- einhverfr 14y agoI dunno. It might depend on which NoSQL folks we are talking about. Certainly the array-native database folks are not even close to the relational use case. I also think the best way to look at NoSQL is that it is just a further development on Stonebreaker's bottom-left quadrant database division--- object databases. The more I get into it, the more I am astounded with the power of PostgreSQL to take over all these workloads on the low-end and more.
- sandGorgon 14y agoI dont know if this is a good idea or not, but IMHO the only way this can happen is to have a postgres compatible version of wordpress.
- ars 14y agoWould that actually be that hard? A MySQL compatibility mode for PostgeSQL would be awesome! It's not even that much to do - support INSERT IGNORE, ON DUPLICATE KEY UPDATE, INSERT REPLACE, and make a "relaxed" mode where too long strings are truncated and NULLs inserted into NOT NULL turn into 0 or the empty string and you are virtually all the way there.
- sandGorgon 14y agointeresting - I was actually thinking of Wordpress having to rewrite its code. But what you said is more interesting - especially since Postgresql already has a SQL Server compatibility (you can replicate from SQL Server to Postgres). It would be a cool kickstarter to fund something like this.
- jeffdavis 14y ago"A MySQL compatibility mode for PostgeSQL would be awesome!" I think it can be good to offer a few conveniences to make it easier to switch, but I think they should be limited in scope. Postgresql is not trying to be mysql -- that need is already filled by MariaDB and others. Trying to pretend that postgres is mysql would just make users frustrated and disappointed. Think about it like moving to a foreign country. The residents try to be as friendly and accommodating as they can when it comes to food, shelter, transportation, directions, etc. There are often even multi-lingual people in the critical places. But eventually the goal is to adapt to the local culture and bring a hint of your previous culture into the mix; not completely recreate your culture in a new place.
- ars 14y agoThey're not that different. They are both SQL, it's just a small amount of extra syntax that MySQL created - useful syntax, and PostgeSQL supports those things. In a different way, sure, but the basic idea of those things is not that different.
- Rhino55 14y agoThis is not a MySQL Problem. This is an Open Source problem.