Re: database navigator for derby
Mr. X. wrote:
I just want to make decisions for using one kind of database that's is
freeware.
David said Derby has problems and is not supported
(Also at link : http://www.profectus.com.au/ee_freedbms.html)
and MySql for some versions is not realy freeware
Actually, although I don't favor MySQL for technical reasons, it truly is
freeware if you use it in conformance with its GPL license. The version
doesn't seem to influence that, only whether you link to their product for
commercial gain.
PostgreSQL, <http://www.postgresql.org/>, is robust, highly scalable, largely
SQL-conformant and has useful extensions. It's especially suitable for those
who swim happily in the world of SQL, with all its views and subqueries and
what-not. It uses the BSD open-source license which is much less restrictive
than GPL for those who wish to (ab)use PG for gain.
<http://www.postgresql.org/about/licence>
MySQL is the /de facto/ standard for web sites, particularly as the "M" in the
widely-adopted "LAMP" (Linux Apache MySQL PHP) architecture. From what I've
read, that model has limits to its scalability. Personally I prefer the more
"enterprisey" approach of heavily-architected strong systems, which favor the
use of Java and PostgreSQL, while still relying on the "L" and "A" components,
adding Tomcat, JSF - MyFaces or the Sun Reference Implementation (RI),
Glassfish or Geronimo or JBoss, maybe a dash of Spring, plus Hibernate or
Apache OpenJPA for the data-access layer.
The choice of architecture is a wholistic one - consider more than just the
database but how to tune all the components. Hardware is relevant. Does your
application justify, or rather, require RAID arrays with battery backed-up
(BBU) caching controllers? Do you make a service guarantee?
That said, I'd still use Postgres over MySQL even for more lightweight use,
since it isn't really complex to manage except as your operational needs make
it so anyway. Thus I favor a LAPJ architecture for web sites, prototypes,
more without bounds.
FWIW, I tried SQuirreL on the recommendations upthread - it works great with
Postgres. I had to tell SQuirreL of the JDBC JAR, which I had previously
downloaded from <http://jdbc.postgresql.org/> to upgrade the default Linux
version. That configuration took about five minutes, the very first five
minutes I had ever used SQuirreL, and it was painless and obvious. Their
splash screen is pretty, too.
<http://squirrel-sql.sourceforge.net/>
--
Lew