Five Questions With Michael Widenius

← Back to Stories (view on slashdot.org)

Five Questions With Michael Widenius

Posted by ScuttleMonkey on Monday February 9, 2009 @07:49AM from the wouldn't-be-open-source-without-drama dept.

volume4 writes "With two MySQL execs leaving Sun in the last week, the internet is buzzing about what is going on at Sun, what is the future of MySQL and what lies ahead for Michael Widenius. Over at Open Source Release Feed, Widenius spoke candidly regarding his split from Sun, the future of MySQL, Monty Program AB, and the open source ecosystem in general."

71 comments

Min score:

Reason:

Sort:

Politics as usual by Anonymous Coward · 2009-02-09 07:57 · Score: 1, Interesting

people in MySQL management made my life hell; They didn't let me participate in MySQL development, didn't give me resources in doing Maria development and did a lot of backstabbing to make my life difficult.
Do you find the politics in the real world more difficult than the ones in the Open Source community?
1. Re:Politics as usual by von_rick · 2009-02-09 08:11 · Score: 3, Interesting
  
  I think this thread is about 5 question for MW that he has already answered :)
  Back to what you said: I think it was mostly the management and less of politics. The role of management is usually to dictate terms that they have absolutely no clue about. A marketing exec managing a SQL functionalities is gonna make the team go sour given enough time.
  
  --
  Face your daemons!
2. Re:Politics as usual by zappepcs · 2009-02-09 08:21 · Score: 4, Insightful
  
  Whether the speculation on reasons for the two leaving is right or not, there is one thing that can be said: MySQL had enough going for it that Sun paid a tidy sum to get it. Whatever they did to cause the 'break up' it was not a good thing.
  Car Analogy: If you buy a racing team; expensive cars, mechanics, drivers... and two star drivers walk out... well, lets just say winner's circle is probably not in your short term future, and the cost of business operations just doubled.
  
  --
  Support NYCountryLawyer RIAA vs People
3. Re:Politics as usual by sunking2 · 2009-02-09 08:42 · Score: 3, Funny
  
  Not if you have Ricky Bobby in the pits.
4. Re:Politics as usual by mb1 · 2009-02-09 09:09 · Score: 1
  
  ...or the beautiful death machine that is ShakeNBakeSQL.
5. Re:Politics as usual by laa · 2009-02-09 18:49 · Score: 1
  
  I think this thread is about 5 question for MW that he has already answered :)
  Fascist! :)
  
  --
  Why does the kernel go through stable and then unstable forks? Can't it always be a stable build, like with Windows?
MySQL to be thrown onto the community? by dov_0 · 2009-02-09 07:59 · Score: 1

While it wouldn't be the first of Sun's projects to go open, maybe they will limit their input into the project and give preference to open source contributions. Maybe take things up again post recession.

--
sudo mount --milk --sugar /cup/tea /mouth /etc/init.d/relax start
1. Re:MySQL to be thrown onto the community? by morgan_greywolf · 2009-02-09 08:11 · Score: 0
  
  Okay, so like 2020 at the soonest?
  
  --
  My blog
2. Re:MySQL to be thrown onto the community? by ShieldW0lf · 2009-02-09 08:18 · Score: 2, Interesting
  
  What a funny interview. He talks all about trust and open source, and yet one of the major reasons I have always avoided open source is because I personally distrusted the two major developers.
  I remember reading countless times how this or that missing feature wasn't needed, and how it was bad practice to use it in the first place. Then, next version, they'd brag that they had it. They would ignore referential integrity, but hide that fact, and call their bugs "Gotchas" or "Features". They would claim that having intelligence in the database and reduce traffic across the wire was bad practice, and that you should move entire result sets into the middle tier and filter it there in their forums, and on and on and on.
  If they had been forthright about what compromises they made, what the strengths and weaknesses of their design were, and been prepared to acknowledge that there were tasks it wasn't fit for, I might have put it to more use. But at the end of the day, I couldn't trust the developers not to engage in misleading behavior, so I stayed far away from it, and used PostgreSQL instead.
  In the end, the developers tried to pull a DivX Networks/Project Mayo type of move and rip off the community, and this was only reversed when Sun bought them out.
  It's good to see that those lying, thieving bastards are no longer involved with the project. Particularly since I am now obligated to use their bastard child at work.
  
  --
  -1 Uncomfortable Truth
3. Re:MySQL to be thrown onto the community? by RichardJenkins · 2009-02-09 09:15 · Score: 1
  
  If the future of MySQL lay in community developer contributions - why bother contributing to MySQL directly? It's all (mostly) still available under the GPL. Form it, and create a community version.
  Sun would never import code back into MySQL unless they owned copyright to it though.
4. Re:MySQL to be thrown onto the community? by Anonymous Coward · 2009-02-09 09:20 · Score: 0
  
  I agree -- any database that does not support foreign keys (referential integrity) is really not a database -- it's just a toy.
  Use Oracle, DB2, or Postgres for any 'real' work.
5. Re:MySQL to be thrown onto the community? by ShieldW0lf · 2009-02-09 09:35 · Score: 2, Interesting
  
  I agree -- any database that does not support foreign keys (referential integrity) is really not a database -- it's just a toy. Use Oracle, DB2, or Postgres for any 'real' work.
  
  See, that's the thing. There are narrow niches where that's a strength, where a little bit of garbage data in there isn't going to cause any harm, and the speed mitigates the weaknesses. And if they had been upfront and forthright about the capacities of the project, that would have been fine.
  
  But when you come across another "not-a-bug-a-gotcha-or-a-feature" every other month that you didn't know about because they were forthright, and you're forced to work with projects that were incredibly poorly designed because people trusted the developers advice and did everything wrong... there isn't any trust there. You couldn't feel safe using it for anything significant unless you're actually getting right in there and hacking it yourself and seeing what it does, because you know from experience that they'd flat out lie to you if they thought it would increase their market share.
  
  --
  -1 Uncomfortable Truth
English is Author's Second Language? by twmcneil · 2009-02-09 08:30 · Score: 0

Am I being picky today or is English the author's second language?

--
"The ferrets, they're every where I tell you!"
1. Re:English is Author's Second Language? by Precision · 2009-02-09 08:51 · Score: 3, Informative
  
  Am I being picky today or is English the author's second language?
  Yes it is, iirc he's from Finland.
  
  --
  - U
2. Re:English is Author's Second Language? by Hordeking · 2009-02-09 08:56 · Score: 0
  
  Am I being picky today or is English the author's second language?
  You're being picky.
  
  --
  Disclaimer: The opinions and actions of the US Gov't are in no way representative of those held by this author or its ci
3. Re:English is Author's Second Language? by grouchyDude · 2009-02-09 10:06 · Score: 1
  
  Not a good enough excuse for a pointless article with little information. Hardly seems to justify promotion to the front page.
4. Re:English is Author's Second Language? by Anonymous Coward · 2009-02-09 10:35 · Score: 1, Interesting
  
  And IIRC his first language is swedish.
Re:Five Questions With Rob Malda... by Red+Flayer · 2009-02-09 08:33 · Score: 0

That's a hell of a lot more than five questions, you twit.

Learn to count.

--
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
Re:Five Questions With Rob Malda... by Anonymous Coward · 2009-02-09 08:47 · Score: 0

I'm not sure what this has to do with Michael Wideanus...maybe you could enlighten us?
It relates to Michael Wideanus because it's referring to your being a nullo, with a wide anus.
Good he could sacrifice a good 30 seconds by ergo98 · 2009-02-09 08:49 · Score: 4, Insightful

My question to him would be "Why? Why send so many naive and misled followers back to Microsoft Access level technology and choices when we should have taken those lessons and moved forward?" MySQL, like PHP, is one of those mistake technologies that thrived despite itself, and when you go to the root of it you find someone saying "I knew nothing about the technology, but just started building from scratch, re-making the mistakes every other product made 20 years earlier".
1. Re:Good he could sacrifice a good 30 seconds by kilodelta · 2009-02-09 09:07 · Score: 2, Interesting
  
  I'm not sure I agree with you at all. LAMP has its place. Put it this way, I've administered MS-SQL, Oracle and MySQL databases, I'll take MySQL any day.
2. Re:Good he could sacrifice a good 30 seconds by ergo98 · 2009-02-09 09:32 · Score: 1
  
  I'm not sure I agree with you at all. LAMP has its place.
  I said nothing about Linux or Apache. LA certainly has its place, though if you look back in the early years of Linux -- remember back when you had to go through a bunch of kernel make files and hand edit all of your driver settings and so on -- there was the same sort of attempt to make lemonade out of lemons that we've seen with MySQL's multi-year mistake. At the time you had to actually compile every driver into the kernel, and this was heralded as a model of efficiency and custom suited kernels, and so on. Then it gained the loadable driver ability, and that farce was quickly discarded. We've seen the same thing with MySQL, where as it finally gains functionality that competitors have had for decades, we're finally hearing the end of the ridiculous "But it's *good* that it has laughable integrity" arguments.
  
  Put it this way, I've administered MS-SQL, Oracle and MySQL databases, I'll take MySQL any day.
  Well since you put it that way...
3. Re:Good he could sacrifice a good 30 seconds by musicmaker · 2009-02-09 09:47 · Score: 5, Insightful
  
  Two words: Explain Plan
  Three More: Share nothing cluster
  A date: '00-00-0000 00:00'
  Two More: Silent truncation
  One acronym: MVCC
  Result: Nobody in their right mind uses MySQL.
  LAMP has it's place, it's at the bottom of a trash heap. Ever tried to write business objects in PHP? What about dependency injection? Database abstraction? (let's face it PDO is a joke). Hell even prepared statements are a pain in PHP/MySQL (only exist in mysqli, and the implementation is horrible). AOP? You can't even do connection pooling for goodness sake because they turned it off in mysqli, and you need your head read if you are using the regular mysql libraries where the solution to injection attacks is to escape quotes and pray. Do you know how long it takes PHP to parse 80,000 lines of libraries every time a script runs because there is no persistence between requests, so PHP has to parse everything over for each request.
  MySQL where foreign keys are silently ignored if you forgot to set your table engine to InnoDB. Where aggregates don't work right, where self referencing updates don't work, so you have to write a program to do what other RDBMSes can do in a single statement. Where your table names are case sensitive, but your text matches aren't.
  Where you don't have sequences to generate globally unique ids, where bit fields work like a boolean half the time and char half the time. Where mysqldump locks half your database and doesn't get everything by default which you find out too late because you didn't know any better.
  Apache where the recommended default for MaxClients is 256, which anybody with a clue knows is insane for dynamic websites, but most sysadmins put in anyway. PHP that hasn't been bothered to update itself to work with a threaded Apache that has been around for a decade.
  I could go on for ages and ages on this stuff. I mean there are SO many issues with LAMP, it's a minefield. LAMP fails when you need it most, when traffic starts getting heavy.
  OR
  you could use a system that separates components into libraries and interfaces, allows you to modularize, allows database independence, makes testing easy, has static typing so the compiler can catch 80% of problems before they ever get executed. Has AOP, has IOC that isn't insane and is used by more enterprise shops that anything else.
  
  --
  Everyone is living in a personal delusion, just some are more delusional than others.
4. Re:Good he could sacrifice a good 30 seconds by anomalous+cohort · 2009-02-09 09:55 · Score: 1
  
  Killing MySql won't send people to MS-Access. It is PostGreSql (which was Sun's original favorite OSS RDMS) that stands to benefit from the death of MySql. I had predicted this a year ago.
5. Re:Good he could sacrifice a good 30 seconds by Anonymous Coward · 2009-02-09 10:16 · Score: 0
  
  Well, you left me hanging... what's the name of the system after the "OR"...
  
  A curious mind wants to know.
6. Re:Good he could sacrifice a good 30 seconds by DragonWriter · 2009-02-09 10:18 · Score: 1
  
  Put it this way, I've administered MS-SQL, Oracle and MySQL databases, I'll take MySQL any day.
  Perhaps, but what about PostgreSQL?
7. Re:Good he could sacrifice a good 30 seconds by Anonymous Coward · 2009-02-09 10:38 · Score: 0
  
  Do you know how long it takes PHP to parse 80,000 lines of libraries every time a script runs because there is no persistence between requests, so PHP has to parse everything over for each request.
  This is false, you can cache the opcodes.
  I could go on for ages and ages on this stuff. I mean there are SO many issues with LAMP, it's a minefield. LAMP fails when you need it most, when traffic starts getting heavy.
  No, the engineers building the system fail. LAMP works perfectly well for my (very large) company.
  Granted, I hate PHP, and very much dislike MySQL, but they aren't billed as "enterprise" solutions, and for good reason.
  Nice Java troll, though. (I'm assuming Java because last I checked .NET didn't do Aspects very well)
8. Re:Good he could sacrifice a good 30 seconds by Anonymous Coward · 2009-02-09 11:45 · Score: 0
  
  This was Sun's plan all along! Spend a billion dollars to kill MySQL and get back to the real database, PostgreSQL! We should be thanking Sun!
9. Re:Good he could sacrifice a good 30 seconds by kilodelta · 2009-02-09 11:57 · Score: 1
  
  Never dealt with PostgreSQL. Did dabble a bit with DB2 though.
10. Re:Good he could sacrifice a good 30 seconds by sarkeizen · 2009-02-09 13:37 · Score: 4, Insightful
  
  There's lots of comment that could be made about that diatribe too.
  First off I'd say that some of this criticism is "Well it doesn't have *buzzword*" mixed with a few statements you are likely not in a position to argue along with a number of things you got wrong enough to betray some ignorance of the subject you are criticizing and at least one instance of "Well the default config doesn't suit what I'm doing". The fact that you have to reach all the way down to that makes me question the "I could go on for ages" bit.
  Considering that you appear to have completely stupid amounts of emotion invested in your particular choice of tools I won't really bother arguing them all.
  One that you mention twice is database abstraction. Personally I'd call DA a double-edged sword. Sure PDO doesn't achieve the level of abstraction that lots of frameworks do (but one might argue that it's not a framework so...) but at least if I hire someone who writes PHP I know they can write a simple join in SQL. I've met huge numbers of people - from professional developers to university students - so mentally locked into a platform that they couldn't do this.
  As an aside one thing I will say about the developers I tend to hire is that they have to show proficiency in writing code in a few different languages and perhaps some aptitude in writing code in a language they've never seen before. One thing I find this cuts down on is the amount of time they spend complaining about language X lacking feature-they-love Y which tends to get in the way of doing actual development.
11. Re:Good he could sacrifice a good 30 seconds by drinkypoo · 2009-02-09 15:01 · Score: 2, Informative
  
  I could go on for ages and ages on this stuff.
  
  You could, but it would be a big fat waste of time, because thousands of people would still use LAMPs for the simple fact that the software costs nothing so hosting is readily available, and there are tons of working content management systems available for free to run on top of them, and by the way numerous commercial sites are doing brisk business with them. So what if they don't fit the needs of HP or Xerox?
  Most of your complaints are about defaults. That's dumb. I mean, the defaults are dumb, but you're still a whiner.
  
  --
  "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
12. Re:Good he could sacrifice a good 30 seconds by sarkeizen · 2009-02-09 15:50 · Score: 1
  
  We have exactly one production Postgres DB in our environment and we will migrate it to MySQL soon. There's a few things that are drivers to this:
  i) DB support on Linux apps - if it runs on Linux it tends to support MySQL but not necessarily postgres (one app I recall running into with this difficulty was wordpress). Because of this the more Linux apps you run, the more you are likely to run a MySQL db which means that even if you standardize on Postgres you will probably break that standard frequently.
  ii) Clustering: The landscape may have changed today but at the time we were trying to get a DB cluster running for failover and performance and although MySQL was ram based it was still better than just about every Postgres solution we looked at.
  iii) MySQL isn't as bad as people think: Most of the time I hear complaints about MySQL they are things like "It isn't ACID compliant". Which is like 'Welcome to four years ago buddy!'. I'm not about to argue that MySQL is equivalent in every respect to Oracle but that for a wide variety of enterprise applications MySQL is sufficient. So much so that a lot of shops might do well do standardize on MySQL and drag Oracle out for that application that can't be moved to anything else.
  Mind you I would like to migrate our MSSQL apps to MySQL as well but there we have the added driver of cost. Not only is the server expensive but clustering seems to, without exception require special more expensive versions of SqlServer and Windows Server. Because of that we are currently using a block-level replication solution for failover and during one of our fire-drill tests the DB was corrupted.
13. Re:Good he could sacrifice a good 30 seconds by Anonymous Coward · 2009-02-09 22:11 · Score: 0
  
  You seem to be blaming a set of tools for your poor development skills. Not a very good argument.
14. Re:Good he could sacrifice a good 30 seconds by Tuntematon · 2009-02-10 00:04 · Score: 1
  
  Ever tried to write business objects in PHP? What about dependency injection? Database abstraction? (let's face it PDO is a joke). Hell even prepared statements are a pain in PHP/MySQL (only exist in mysqli, and the implementation is horrible). AOP?
  I don't even know what the these terms mean so it must mean I can still use MySQL and it has a place after all?
  
  --
  By Tuntematon
15. Re:Good he could sacrifice a good 30 seconds by Anonymous Coward · 2009-02-10 02:09 · Score: 0
  
  Can anyone explain how to script backups of dbs that table type, a db with another type, and a db with mixed types
16. Re:Good he could sacrifice a good 30 seconds by toby · 2009-02-10 03:19 · Score: 1
  
  Why ask Monty? Why not ask every major web player on the planet why they choose 'Microsoft Access level technology'.
  You might find yourself laughed out of the room (as Microsoft would be, if they tried to sell Access to Google, Yahoo, Flickr, Slashdot, imdb, SABRE, YouTube, Wikipedia, NASA, US Census, ... and most major MySQL users).
  http://mysql.com/why-mysql/case-studies/
  http://mysql.com/customers/
  
  --
  you had me at #!
17. Re:Good he could sacrifice a good 30 seconds by Slashdot+Parent · 2009-02-10 03:36 · Score: 1
  
  you could use a system that separates components into libraries and interfaces, allows you to modularize, allows database independence, makes testing easy, has static typing so the compiler can catch 80% of problems before they ever get executed. Has AOP, has IOC that isn't insane and is used by more enterprise shops that anything else.
  I'm curious on this one. When is the last time you swapped out one database for another?
  Also, can you name a few good uses for AOP other than trace-level logging and security? I'm not trolling, I just really wish I knew the answer and I've been asking everyone who sounded like they could give one to me.
  
  --
  They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
18. Re:Good he could sacrifice a good 30 seconds by ergo98 · 2009-02-10 04:41 · Score: 1
  
  Why ask Monty? Why not ask every major web player on the planet why they choose 'Microsoft Access level technology'.
  You realize that MySQL wasn't invented yesterday, right? That it has plied its course for some 14 years now.
  For about the first 7 of those, it was absolutely horrific, chosen only by idiots who had absolutely no idea what they're doing. Since then, sure it has started to gain features that every other RDBMS vendor has had long before, with each step the naive userbase suddenly coming into realization of what they were missing, finally abandoning the hilarious rhetoric they'd been spouting online since.
  Though it's funny that now we're doing it all again with products like CouchDB. I laughed when I watched the video of the Damien guy where he professes to having started with no idea about databases, but why let them stop him? The history of MySQL follows the same sad tale. In both cases, people afraid of real databases just clutch onto their talking points and rhetoric and tell us that their super ridiculous chosen technology is somehow superior in its inferiority.
19. Re:Good he could sacrifice a good 30 seconds by Simetrical · 2009-02-10 12:52 · Score: 1
  
  Where mysqldump locks half your database
  FWIW, if you use it with InnoDB (and almost any serious MySQL shop uses InnoDB exclusively), mysqldump --single-transaction is lockless.
  
  --
  MediaWiki developer, Total War Center sysadmin
20. Re:Good he could sacrifice a good 30 seconds by crucini · 2009-02-15 04:58 · Score: 1
  
  ...and almost any serious MySQL shop uses InnoDB exclusively...
  I work at a pretty serious MySQL user, and we use both MyIsam and InnoDB. Properly tuned and used, Isam is faster. Innodb allegedly has the edge in PK-lookups, but my measurements disagree.
  Innodb is good if you want Oracle-ish features. Mostly we don't. In fact, the current is flowing the other way; towards things even leaner than MySQL.
  We mysqldump the slave, which eliminates that issue. (You can also stop the slave and cp the db files; I think this does not work with Inno). Table locks remain a serious performance issue in Isam; it does take extra effort to prevent lock contention.
21. Re:Good he could sacrifice a good 30 seconds by Simetrical · 2009-02-15 05:14 · Score: 1
  
  I work at a pretty serious MySQL user, and we use both MyIsam and InnoDB. Properly tuned and used, Isam is faster. Innodb allegedly has the edge in PK-lookups, but my measurements disagree.
  InnoDB also doesn't have to be repaired or checked. MyISAM tables can crash on occasion if you look at them funny, and then you have to spend an inordinate amount of time repairing the tables (possibly days for large data sets). InnoDB supports data clustering, which is extremely useful for disk-bound data sets. And table-level locking in MyISAM is prohibitive for most serious workloads, unless either there are no writes (other than end-of-table inserts) or all of your queries are fast.
  I'm curious: how large are the tables at your shop, and how many reads/writes per second do you have? I know that Wikipedia, for instance, would melt if you tried using MyISAM anywhere, and it's no more than a mid-sized MySQL user as far as its database size goes.
  
  We mysqldump the slave, which eliminates that issue. (You can also stop the slave and cp the db files; I think this does not work with Inno).
  It does, in my experience (with the usual version-mismatch caveats), but only if you copy the entire MySQL data directory. Some essential parts of the InnoDB data files are shared across all tables and can't be split out by simple filesystem commands.
  
  --
  MediaWiki developer, Total War Center sysadmin
Question: What is #4? by PPH · 2009-02-09 08:50 · Score: 0

We know that #5 is "Profit!"

--
Have gnu, will travel.
Five Questions... by RayMarron · 2009-02-09 08:56 · Score: 2, Informative

...three of which were answered "See my blog". Article rated -1 uninformative.

--
ON DELETE CASCADE
1. Re:Five Questions... by quickOnTheUptake · 2009-02-09 09:08 · Score: 2, Interesting
  
  I got the distinct feeling he was kinda fed up with the interviewer.
  I liked the "I just answered that." It takes real skill to get someone to answer like that in a short non-controversial interview.
  
  --
  Mod points: Guaranteed to remove your sense of humor.
  Side effects may include gullibility and temporary retardation
2. Re:Five Questions... by Dynedain · 2009-02-09 09:36 · Score: 1
  
  I disagree. His "I just answered that" response was referring the interviewer/reader to the previous question, to which his answer was basically "Read my blog".
  The blog link is a post to a mostly-empty, non-informative wiki. If you aren't going to answer the questions, don't take the interview. This was just a cop-out of "I'm to lazy to explain things to you, figure it out yourself" which is a horrible stance to take when you're trying to launch a new venture and gain interest.
  
  --
  I'm out of my mind right now, but feel free to leave a message.....
3. Re:Five Questions... by musicmaker · 2009-02-09 09:51 · Score: 1
  
  It's yet another demonstration of the professionalism of the MySQL people. Maybe Sun can introduce some level of seriousness about software to MySQL. Oh wait - those are the people that gave us Java; nevermind.
  
  --
  Everyone is living in a personal delusion, just some are more delusional than others.
4. Re:Five Questions... by Anonymous Coward · 2009-02-09 10:22 · Score: 0
  
  I really doubt that this was a face-to-face interview. My guess is that the five questions were e-mailed to him all at the same time.
Is it me... by Anonymous Coward · 2009-02-09 09:02 · Score: 0

Or did that page just get /.'ed...can't seem to load it.
MyStinkQL by Anonymous Coward · 2009-02-09 09:49 · Score: 0

I'm not under a rock or new to open source and yet I still don't want to run MySQL.
before open source? by sl0ppy · 2009-02-09 09:54 · Score: 1

David Axmark (the second founder of MySQL) and I released it 'open source like' (this was before open source) in 1995
i think that several people would disagree with that.
mySQL was seen at the time as an answer to mSQL, which was non-free, even to the point of sharing a very similar API.
funny how times and history change.
1. Re:before open source? by Anonymous Coward · 2009-02-18 05:47 · Score: 0
  
  Duh open source vs Free Software duh.
  Open source is commonly accepted as coming into being when Netscape freed Mozilla (~1998). Free Software has existed for ages it's true.
  How about you read some history, and some definitions.
Screw microsoft! by Anonymous Coward · 2009-02-09 10:32 · Score: 0

amirite?
What's the next big DB? by EmperorOfCanada · 2009-02-09 11:55 · Score: 1

Obviously not an emergency, but what is going to be the next big DB? Obviously SUN is going to screw up MySQL sooner or later (if not a bit already). I really don't want to develop for the next few years without knowing what DB I am going to end up switching to. Will PG reemerge from its slumber? Will someone fork or branch MySQL? Will SUN go under and MySQL break free (1 billion $ later)? Firebird looks vaguely interesting. So my question would be: If your boss was allergic to MySQL what would your next choice be? My next question is: How will SUN screw up MySQL? Java based trigger language, Build up of annoying bugs, Proprietary high cost "Enterprise" version with critical features, A "rebuild" that completely ruins the whole thing, A tacky marketing program that makes people embarrassed to say MySQL, A new name that costs 3 million or more. Pointless features that support some other SUN marketing effort, ... and my favorite ... Neglect.
1. Re:What's the next big DB? by Frankenshteen · 2009-02-09 12:37 · Score: 1
  
  I think the big fork is already available from Google. And with their investment in MySQL, it can't go away anytime soon. http://code.google.com/p/google-mysql-tools/downloads/list
  
  --
  "It's a doughnut stuffed with M&M's. That way when you finish the doughnut, you don't have to eat any M&M's."
2. Re:What's the next big DB? by Anonymous Coward · 2009-02-09 12:51 · Score: 0
  
  "what is going to be the next big DB?"
  The next open source big DB, I think you meant.
  Well, of course PostgreSQL, as it has always been (if only it were distributed under GPL instead of BSD...)
3. Re:What's the next big DB? by Anonymous Coward · 2009-02-09 13:10 · Score: 0
  
  What's the next big DB?
  CouchDB.
  with its RESTful interface, its map/reduce functionality, its ability to scale huge, and its simplicity of replication, i'd have to say CouchDB in a heartbeat. especially as data gets bigger, and data warehousing becomes more important.
  of course, this also means moving more of the software and business logic into the database, and that's the opposite direction of mySQL.
4. Re:What's the next big DB? by Anonymous Coward · 2009-02-13 00:54 · Score: 0
  
  > if only it were distributed under GPL instead of BSD...)
  Huh?
Slashdotted by rrohbeck · 2009-02-09 13:30 · Score: 1

Coral cache:
http://www.opensourcereleasefeed.com.nyud.net/interview/show/five-questions-with-michael-widenius-founder-and-original-developer-of-mysql

--
thegodmovie.com - watch it
No URL in your comment... by drinkypoo · 2009-02-09 13:52 · Score: 1

...even though it's about "See my blog." Your comment is -1 uninformative.

--
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
1. Re:No URL in your comment... by RayMarron · 2009-02-10 02:17 · Score: 1
  
  The URL is present in the FA. I'm simply normalizing the comment data.
  
  --
  ON DELETE CASCADE
product by Anonymous Coward · 2009-02-09 19:06 · Score: 0

with 2 sides
commercial OR
functional
it's totally different
Got it: if you're incompetent, don't use MySQL by Anonymous Coward · 2009-02-09 23:33 · Score: 0

Your comment comes down to saying that if you're incompetent you shouldn't be writing applications with MySQL. Big surprise. Not. You should be fired instead.
Finland? by Dr.+Cody · 2009-02-10 01:44 · Score: 1

I though he was from Christmas Island.
Oh, wait...
How well do you know MySQL? by toby · 2009-02-10 03:12 · Score: 1

InnoDB does support foreign key constraints. (And I'll mention that it has ACID transactions as well, since you may not know that either.)

--
you had me at #!
1. Re:How well do you know MySQL? by ShieldW0lf · 2009-02-19 06:15 · Score: 1
  
  InnoDB does support foreign key constraints. (And I'll mention that it has ACID transactions as well, since you may not know that either.)
  
  Well, actually, InnoDB was made by another group and is currently "owned" by Oracle if I'm not mistaken. Regardless, I remember when they didn't have these things, and they constantly put forth that they were some backwards way of doing things that was unjustified and that if you were doing things right, you didn't need them. This isn't about features. It's about trust.
  
  --
  -1 Uncomfortable Truth