Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Oracle makes move to kill open source MySQL

techcrunch.com

Post reply on HN
Print view View original

41–50 of 97 posts

Re: Oracle makes move to kill open source MySQL

#41

Post by crag »

Sauce1971 wrote: post #34

I used to enjoy working with Oracle databases, but the horrible pricing and high need for dba maintenance was always discomforting. Switch for a while to MSSQL, but then the market for Windows apps disappeared. Have been using mySQL with very little sort of DB satisfaction. Now I don't know why anyone would not choose PostgreSQL for almost any project. Oracle is a bad apple, making money with methods aking to extorti…

I still wonder why SQLite isn't used more. Granted for busy large sites/applications SQLite is the wrong tool. But most sites using MySQL are small.

Re: Oracle makes move to kill open source MySQL

#42

Post by paulgb »

crag wrote: post #41
Sauce1971 wrote: post #34

I used to enjoy working with Oracle databases, but the horrible pricing and high need for dba maintenance was always discomforting. Switch for a while to MSSQL, but then the market for Windows apps disappeared. Have been using mySQL with very little sort of DB satisfaction. Now I don't know why anyone would not choose PostgreSQL for almost any project. Oracle is a bad apple, making money with methods aking to extorti…

I still wonder why SQLite isn't used more. Granted for busy large sites/applications SQLite is the wrong tool. But most sites using MySQL are small.

My experience with SQLite is that if you're using it as more than an object-store, you'll be disappointed by the limited subset of SQL it supports. And if you do just need an object store, Mongo is often a better fit and gives you flexible schema.

That said, as an embedded DB I would use SQLite.

Re: Oracle makes move to kill open source MySQL

#43

Post by derpmeister »

fredsanford wrote: post #21
Nogwater wrote: post #9

Earlier quoted context omitted.

I don't know anything about Firebird. Is it really a good replacement for MySQL?

I found it to be pretty solid and fast when I last used it, which was right after Borland Open-Sourced it. It was forked from Interbase.

Postgres is developing a lot quicker then Firebird. Also, management and replication solutions for Postgres are far more advanced. But what matters most (for me) is documentation. I can find everything I need to know right here:

http://www.postgresql.org/docs/9.1/interactive/sql-commands....

Re: Oracle makes move to kill open source MySQL

#44

Post by derpmeister »

lttlrck wrote: post #35
mbreese wrote: post #11

Earlier quoted context omitted.

Unfortunately, that includes hardware too... A friend had 3 out of 13 Oracle servers die with random memory errors (persistent). Of course, if they had a 10K+ service contract they'd be happy to help.

How much did it cost to replace those 3 servers? >10K I bet...

This reeks of extortion. Let's sell the rejects to the customers without a support contract. That'll teach 'em.

Re: Oracle makes move to kill open source MySQL

#45

Post by jeffdavis »

crag wrote: post #41
Sauce1971 wrote: post #34

I used to enjoy working with Oracle databases, but the horrible pricing and high need for dba maintenance was always discomforting. Switch for a while to MSSQL, but then the market for Windows apps disappeared. Have been using mySQL with very little sort of DB satisfaction. Now I don't know why anyone would not choose PostgreSQL for almost any project. Oracle is a bad apple, making money with methods aking to extorti…

I still wonder why SQLite isn't used more. Granted for busy large sites/applications SQLite is the wrong tool. But most sites using MySQL are small.

Disclaimer: It's been a while since I tried to use SQLite for anything.

I've never really felt that it was actually easier to use than a client/server DBMS. I can imagine that it's good for some kinds of embedded applications, but for normal web applications I don't see any improvement in usability. Juggling files is not any easier than setting up a connection.

And there were always annoyances associated with the simplicity. All those "complex features" in a real DBMS turn out to be useful sooner than you think (and I don't mean "once in production" I mean while still in development). Even the simplest applications can usually benefit from good support for dates and times.

I think SQLite just drew the line in the wrong place for most applications (although it may serve a niche quite well). Oversimplification requires the developer to reinvent, which results in a much more complex system overall (or one that at least requires more work to develop and maintain). Key/value stores have similar problems for general-purpose application development.

Re: Oracle makes move to kill open source MySQL

#46

Post by army »

spudlyo wrote: post #30

This test-case controversy was both discovered and ginned up by Monty and the MariaDB folks, who have much to gain by the rejection of Oracle's brand of MySQL and the promotion of MariaDB. While it may be part of some larger and sinister plan to "kill" open source MySQL as the article suggests, it seems more likely to me that it was simply a mistake, and one they'll walk back at some point. If it is an anti-competiti…

From what I've heard withholding test cases is actually official Oracle policy, unlike, for example, the lack of updates to the launchpad repository. There wasn't any deliberate attempt to without commit history from launchpad - they were just slow in updating it.

Re: Oracle makes move to kill open source MySQL

#47

Post by spudlyo »

jeffdavis wrote: post #37
spudlyo wrote: post #30

This test-case controversy was both discovered and ginned up by Monty and the MariaDB folks, who have much to gain by the rejection of Oracle's brand of MySQL and the promotion of MariaDB. While it may be part of some larger and sinister plan to "kill" open source MySQL as the article suggests, it seems more likely to me that it was simply a mistake, and one they'll walk back at some point. If it is an anti-competiti…

"it seems more likely to me that it was simply a mistake, and one they'll walk back at some point." How do you explain removing access to the source repository then? Or the fact that the documentation is not free to redistribute?

How do you explain removing access to the source repository then?

I can easily explain it, because it never happened. Access to the MySQL source repository on launchpad is available for anyone to browse. Oracle is occasionally lazy about updating it, but they've never removed access AFAIK.

Or the fact that the documentation is not free to redistribute?

The documentation has never been free to redistribute, it was that way under Monty, it was that way under Sun, and it remains that way under Oracle.

Re: Oracle makes move to kill open source MySQL

#48

Post by army »

meritt wrote: post #28
dj2stein9 wrote: post #16

As mentioned in the comments see MariaDB ( http://mariadb.org/ ), an open source fork of MySQL from before the Oracle acquisition. Like Hudson, MySQL will live on.

I've been using Percona for a number of years now. Are there any solid comparisons between Percona and MariaDB?

I don't think Percona sees itself as a fork: it is just MySQL + special Percona patches.

Re: Oracle makes move to kill open source MySQL

#49

Post by nahname »

crag wrote: post #41
Sauce1971 wrote: post #34

I used to enjoy working with Oracle databases, but the horrible pricing and high need for dba maintenance was always discomforting. Switch for a while to MSSQL, but then the market for Windows apps disappeared. Have been using mySQL with very little sort of DB satisfaction. Now I don't know why anyone would not choose PostgreSQL for almost any project. Oracle is a bad apple, making money with methods aking to extorti…

I still wonder why SQLite isn't used more. Granted for busy large sites/applications SQLite is the wrong tool. But most sites using MySQL are small.

SQLite is not a real solution for anything needing to support more than one user at a time. It's fine for things like managing bookmarks within firefox, but not for a full relational database replacement. The write access is single threaded (at least last time I used it).

Re: Oracle makes move to kill open source MySQL

#50

Post by ibotty »

spudlyo wrote: post #30

This test-case controversy was both discovered and ginned up by Monty and the MariaDB folks, who have much to gain by the rejection of Oracle's brand of MySQL and the promotion of MariaDB. While it may be part of some larger and sinister plan to "kill" open source MySQL as the article suggests, it seems more likely to me that it was simply a mistake, and one they'll walk back at some point. If it is an anti-competiti…

it does not matter to simple rhel rebuilds like centos or scientific linux. it is unfortunate for the linux stable kernel maintainers. that's for sure though.

it is very different from this case. that it's a simple mistake is not very probable. see the java sec update controversy a few days ago.

Post reply on HN