Linked by Thom Holwerda on Wed 18th Oct 2006 16:58 UTC, submitted by wirespot
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."
Permalink for comment 172808
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
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!