which database is better with JAVA ?

> > Pick a flavor licensed (oracle) or unlicensed

> > (MySQL). How you use them is essentially the same

> > (only slight, although sometimes major,

> differences

> > in the SQL statements).

>

> Actually, they're very different in terms of

> referential integrity, sequences, constraints, stored

> procedures, triggers, etc . Not the same at all.

>

And I would add not the same in performance as well, particularly with larger scale operations.

If I was given the choice between the two I would choose Oracle. Yes MySQL is free but there is a maxim (or there should be) "you get what you pay for".

MySQL is fine for some situations but it is NOT an enterprise solution because in terms of performance alone it scales very poorly (lack of table statistics for one thing).

cotton.ma at 2007-7-15 5:19:19 >

I was saying in how they are used (jdbc wise). There are of course major differences in performance and operational ability in the Databases themselves, but as far as the coding it is essentially the same (except of course for the actual SQL). Had he mentioned any requirements, other than the jdbc connection, I would obviously have given a better answer. But that question was just too open ended and so I gave a very general answer, but only in scope of the question (the connection from java to db and the coding).

There are also many other factor involved, and many other DBs to choose from (Sybase, Informix, DB2, SleepyCat, etc.). But from that question, you cannot excpect a good answer. So I gave the only one that fits which was, choose between a commercial or open-source db

as befits your situation.

It was much to general and flippant, and so I probably deserved to be flamed, but please don't think I'm an idoit or ignorant of the issues.

masijade.a at 2007-7-15 5:19:19 >

> your question is too general but i prefer oracle for large projects

As long as somebody else is paying the license fee.

> and mysql for small projects.

And this contributes what new information to the discussion?

>

> you might also consider using postgresql. also an

> open-source but much better than mysql :-)

Much better, indeed. Thanks for the second.

> you might also consider the use of

> object-relational-mapping (ex.hibernate)

> for your database and application so your application

> written

> on java wont be much dependent on the database :-)

Your application won't be any less dependent on the database. It will make it possible to switch databases just by changing the Hibernate dialect.

I would not recommend Hibernate to someone who has to ask this question.

%

duffymoa at 2007-7-15 5:19:19 >