Re:The State of MySQL: The Elephant in the Room
by wheels on Wednesday February 11, 2009 @01:11AM
(#476631)
That's not really true. They both do it so that they have the ability to relicense the code to their ends and defend any legal challenges against the code-base as a whole. If MySQL just wanted to be able to use the contributed code they could simply require that it be under a less restrictive license (BSD, MIT, etc.)
Re:The State of MySQL: The Elephant in the Room
by davidw on Tuesday February 10, 2009 @03:09PM
(#475826)
Yeah, that's a good point. Well, like I said, I am firmly in the Postgres camp in any case. I've never enjoyed discovering things about Mysql like the fact that even InnoDB doesn't allow you to modify the DB transactionally.
Re:The State of MySQL: The Elephant in the Room
by ruby_roo on Tuesday February 10, 2009 @07:36PM
(#476268)
Wait... what?
Looks like InnoDB supports transactions, no? http://dev.mysql.com/doc/refman/5.1/en/innodb-transaction-mo...
Re:The State of MySQL: The Elephant in the Room
by davidw on Wednesday February 11, 2009 @01:22AM
(#476642)
http://adam.blog.heroku.com/past/2008/9/3/ddl_transactions/
"MySQL doesn’t support DDL transactions;"
Meaning you can't change the schema transactionally. InnoDB handles data transactions ok, but I hadn't realized that it doesn't handle schema changes. It seems like I'm always discovering some little nasty about Mysql when I am forced to use it.
The FSF uses copyright assignment to ensure that open source code is not legally encumbered.
MySQL uses the copyright assignment so they can sell code contributed by open source developers in their commercial platform without compensating the authors.