Well well well. I can see this working well for Oracle - they use Java a great deal... and it should be good news for Sun's open source projects like Netbeans - which would, I think, be maintained under Oracle.
I guess it's a little sad to see Sun unable to continue by themselves, but the writing was on the wall and I think Oracle will keep all the Sun products working, but of course the big question is what does this mean for MySQL?
It remains a functional relational database. It has a BSD-style license with a very stable, nearly bug-free (see Coverity) core. It has modular design (you can write procedures in Java, C, C++, T/SQL, R, Python and others. You can get commercial support from a company (EnterpriseDB) that doesn't have a vested interest in moving you to a very expensive alternative.
I had a fairly major system I created and that's one of the two reasons I used another db - case sensitivity and the nonsensical naming of database/table files. Imagine this - I need to grab the physical file for a db or table.... what do I look for? The db or table name with some extension? No, I have to figure out what the nonsensical, internal name is for it. Retarded crap.
Imagine this - I need to grab the physical file for a db or table.... what do I look for?
Imagine this - you'd never, ever want to do that with a production database. What good is a copy of a table file with no context, no foreign key integrity, no transactional integrity, nothing? If you must back up a single table, pg_dump works.
I don't have anything against Mysql, and it does what it's meant to do just fine, but it isn't a fully featured db, and attempts to use it for that usually end up with people doing half the query in their code instead of in the db, where queries are meant to be run.
What about MySQL? (Score:5, Interesting)
Well well well. I can see this working well for Oracle - they use Java a great deal... and it should be good news for Sun's open source projects like Netbeans - which would, I think, be maintained under Oracle.
I guess it's a little sad to see Sun unable to continue by themselves, but the writing was on the wall and I think Oracle will keep all the Sun products working, but of course the big question is what does this mean for MySQL?
Postgres is looking better than ever (Score:5, Informative)
Re: (Score:1)
Re: (Score:0)
I had a fairly major system I created and that's one of the two reasons I used another db - case sensitivity and the nonsensical naming of database/table files. Imagine this - I need to grab the physical file for a db or table.... what do I look for? The db or table name with some extension? No, I have to figure out what the nonsensical, internal name is for it. Retarded crap.
Re: (Score:5, Informative)
Imagine this - I need to grab the physical file for a db or table.... what do I look for?
Imagine this - you'd never, ever want to do that with a production database. What good is a copy of a table file with no context, no foreign key integrity, no transactional integrity, nothing? If you must back up a single table, pg_dump works.
Re: (Score:4, Insightful)
What good is a copy of a table file with no context, no foreign key integrity, no transactional integrity
Dude, you're talking to a MySQL user. They don't know what those things are.
Re: (Score:2)
I disagree. They know what they are, but they've been told that they're unimportant.
if i had mod points today, you'd get some (Score:2)
I don't have anything against Mysql, and it does what it's meant to do just fine, but it isn't a fully featured db, and attempts to use it for that usually end up with people doing half the query in their code instead of in the db, where queries are meant to be run.