Linked by Thom Holwerda on Wed 18th Oct 2006 16:58 UTC, submitted by wirespot
Databases The popular MySQL database is slated for a future split between what MySQL AB calls the Community and the Enterprise versions. Read the official announcement and further opinions and explanations from Kaj Arno (MySQL VP of Community Relations) and Stephen O'Grady (software industry analist). In Arno's own words: "We recognise that the needs of the MySQL Community are different from the needs of commercial enterprise customers. After 11 years of producing our software, we can no longer hope that a single offering is the best solution for both Community and Enterprise users. Consequently, we are introducing two different offerings for each distinct target group."
Thread beginning with comment 172801
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Should have seen this coming.
by justinbest on Wed 18th Oct 2006 18:51 UTC in reply to "Should have seen this coming."
justinbest
Member since:
2006-06-29

Read the announcement.

"ALL OF OUR DATABASE SOFTWARE IS OPEN SOURCE, so we will continue to make all releases available over our BitKeeper tree and as source code tarballs"

They aren't taking away our access to the source. They're simply putting out binaries for customers that want them.

I use PostgreSQL right now, but I've been wanting to switch to MySQL ever since their 5.0 release. The announcement of a more targeted business support structure makes me all the more eager to use MySQL.

Reply Parent Score: 1

ormandj Member since:
2005-10-09

You're the ONLY person I've EVER met who is using pgsql and wants to switch to a less functional database server. That's like getting rid of your "free" BMW and getting a "free" Yugo. Buying into hype/popularity/branding, per-chance? I hope you don't go that route, because it's going to make life hell for your SQL devs and worse yet for your system admins. I sure hope your database isn't used for mission critical transactional processing where data integrity AND validity is key.

I did read the announcement. However, history dictates what will likely occur. I simply postulated as to what will happen, and my opinion is as valid as anybody else's.

Regardless, good luck with your migration, I wish you all the best - but I do hope you listen to reason instead of "buzz". ;)

Reply Parent Score: 5

justinbest Member since:
2006-06-29

Thanks for the advice. No, it's not the "buzz" that I want. My project is a small, in-house data analysis tool written by me, for me. I'm tired of dealing with the quirks of PG (vacuuming all the time, lack of easy-to-set-up performance monitors, etc.)

It could just be my lack of knowledge, but enforcing data integrity with anything over 300,000 rows in my table seems to cause more hassle than help. Performance grinds to a halt with all those internal consistency checks. I didn't experience performance issues back before I rewrote the project to use PG (I used MySQL previously).

So, even though I know I will have to do some extra work client-side, I think the tradeoff will be worth it. We'll see if I ever have the spare time to find out, though!

Reply Parent Score: 2