Oracle makes move to kill open source MySQL • Hacker News Board

Re: Oracle makes move to kill open source MySQL

#71

Post by killedbydeath » Sun, Sep 02, 2012, 9:50 PM UTC

taligent wrote: post #63

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…

>Now I don't know why anyone would not choose PostgreSQL for almost any project. No offense but people who make statements like this clearly don't know much about the current state of databases. PostgreSQL is pretty bad in many areas compared to the newer databases e.g. ease of clustering and sharding, developer friendliness, JSON support, tool support etc. It's great as a replacement for a typical RDBMS but if you'r…

Not sure what you mean by lack of developer friendliness and what specific tools you find it lacking. Postgres is a great choice for new startups that need an RDBMS and like having schema for their data. There is built-in JSON support in upcoming 9.2 release and most JSON-to-schema mapping should be done in application anyway. Sharding is easy to do at application level; you would lose ability to do certain queries across shards but most solutions offering automatic sharding are designed specifically not to allow most types inter-shard querying and instead offer map-reduce.

Re: Oracle makes move to kill open source MySQL

#72

Post by TazeTSchnitzel » Sun, Sep 02, 2012, 9:54 PM UTC

quesera wrote: post #70

TazeTSchnitzel wrote: post #67

Earlier quoted context omitted.

Well, personally, my favourite database is SQLite. I don't build large apps, although for many-read-few-write-type sites SQLite isn't so bad.

SQLite is awesome too. I use it whenever I can.

I personally like its simplicity, like the fact it's a single file and no messy authentication to deal with, and the simple data type set.

And also the docs are much more readable to me than for MySQL.

Re: Oracle makes move to kill open source MySQL

#73

Post by taligent » Sun, Sep 02, 2012, 10:03 PM UTC

killedbydeath wrote: post #71

taligent wrote: post #63

Earlier quoted context omitted.

>Now I don't know why anyone would not choose PostgreSQL for almost any project. No offense but people who make statements like this clearly don't know much about the current state of databases. PostgreSQL is pretty bad in many areas compared to the newer databases e.g. ease of clustering and sharding, developer friendliness, JSON support, tool support etc. It's great as a replacement for a typical RDBMS but if you'r…

Not sure what you mean by lack of developer friendliness and what specific tools you find it lacking. Postgres is a great choice for new startups that need an RDBMS and like having schema for their data. There is built-in JSON support in upcoming 9.2 release and most JSON-to-schema mapping should be done in application anyway. Sharding is easy to do at application level; you would lose ability to do certain queries a…

Sorry but PostgreSQL's JSON support is a joke. It is nothing more than a VARCHAR that validates. You can't search or index across fields and the way you actually query the JSON is cumbersome at best.

Also all of your arguments are "push to the application layer". Well my point is that with most of the newer databases you don't have to reimplement the wheel.

Re: Oracle makes move to kill open source MySQL

#74

Post by [deleted] » Sun, Sep 02, 2012, 10:08 PM UTC

crag wrote: post #38

mtgx wrote: post #20

It seems Oracle is on a trend to kill everything open source they've acquired from Sun. Java seems to be the only one left, and it would've happened already if they won the trial with Google, but I'm sure they'll do something equally dumb in the future to kill finally Java, too.

There are other open source projects at Oracle that are still "alive". Like Netbeans.

[deleted]

Re: Oracle makes move to kill open source MySQL

#75

Post by Legion » Sun, Sep 02, 2012, 10:12 PM UTC

mtgx wrote: post #20

It seems Oracle is on a trend to kill everything open source they've acquired from Sun. Java seems to be the only one left, and it would've happened already if they won the trial with Google, but I'm sure they'll do something equally dumb in the future to kill finally Java, too.

Well, there are some projects still going. But the joke is:

Q: Why hasn't Oracle ruined Virtualbox yet?

A: Because they're going in alphabetical order.

Re: Oracle makes move to kill open source MySQL

#76

Post by 4ad » Sun, Sep 02, 2012, 10:22 PM UTC

taligent wrote: post #64

quesera wrote: post #61

Earlier quoted context omitted.

MySQL and Java don't affect me much personally, but I think the way they've handled Solaris is a real tragedy for the industry. Larry is the new Bill. I blame Jonathan.

What's happening to Solaris ? It is still open and available for download at http://opensolaris.org . It just isn't being supported by Oracle anymore since they are focused on Oracle Linux.

No, the gate has been closed about two years ago. Solaris is not open source anymore. The illumos guys forked the last available version of the code and push it forward independently.

Re: Oracle makes move to kill open source MySQL

#77

Post by fooyc » Sun, Sep 02, 2012, 10:28 PM UTC

taligent wrote: post #63

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…

>Now I don't know why anyone would not choose PostgreSQL for almost any project. No offense but people who make statements like this clearly don't know much about the current state of databases. PostgreSQL is pretty bad in many areas compared to the newer databases e.g. ease of clustering and sharding, developer friendliness, JSON support, tool support etc. It's great as a replacement for a typical RDBMS but if you'r…

> ease of clustering and sharding, developer friendliness, JSON support, tool support etc.

Which RDBMS do you have in mind ?

Re: Oracle makes move to kill open source MySQL

#78

Post by taligent » Sun, Sep 02, 2012, 10:52 PM UTC

fooyc wrote: post #77

taligent wrote: post #63

Earlier quoted context omitted.

>Now I don't know why anyone would not choose PostgreSQL for almost any project. No offense but people who make statements like this clearly don't know much about the current state of databases. PostgreSQL is pretty bad in many areas compared to the newer databases e.g. ease of clustering and sharding, developer friendliness, JSON support, tool support etc. It's great as a replacement for a typical RDBMS but if you'r…

> ease of clustering and sharding, developer friendliness, JSON support, tool support etc. Which RDBMS do you have in mind ?

Well some are better than others right. Riak/CouchDB are great when it comes to clustering/sharding. MongoDB has the best JSON support and is very friendly for developers. MySQL is proven, has the best tool support and most widely supported.

The fact is that just like one programming language doesn't satisfy all use cases. Neither does one database. So maybe PostgreSQL 'supporters' should stop trying to claim it is perfect for everyone.

Re: Oracle makes move to kill open source MySQL

#79

Post by pstuart » Sun, Sep 02, 2012, 11:01 PM UTC

crag wrote: post #57

jeffdavis wrote: post #45

Earlier quoted context omitted.

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 sim…

1. With the PDO (or any ORM) setting up and "using" SQLite is as easy as any other database. 2. There are several really nice front-ends to SQlite, along with the phpmyadmin like app for SQlite. Like MySQL you'll never have to use the command line (for most operations). 3. SQLite is now included with just about every scripting language (except MS' langs - where it's just a matter of downloading the app and an ODBC dr…

You can write to a view via triggers.

Re: Oracle makes move to kill open source MySQL

#80

Post by xentronium » Sun, Sep 02, 2012, 11:05 PM UTC

nahname wrote: post #49

crag wrote: post #41

Earlier quoted context omitted.

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).

Well, mongo has write lock too, and people seem to use it a lot.