Quoting Steven Woody <[EMAIL PROTECTED]>:

> Hi, folks
> 
> MySQL and PostgreSQL, which one is the better choice for tomcat ?
> 
> --
> Steven Woody
> [EMAIL PROTECTED]
> 
[OT] isn't it ;) 

First, I do not see in which regards a database choice might be linked to a JSP
container ? Nevertheless ...


Postgresql:

I have a very satisfied experience using Postgresql in terms of deployment
simplicity, reliability, features and performances.

I moved from Oracle to Postgresql four years ago. At that time the reasons I
choose Postgresql and not MySql were some features I was looking for like stored
procedures, triggers and foreign keys were not supported in MySql.


A very productive "embrace all db" alternative:

You might consider investing your time acquiring knowlege of a persistence layer
like Hibernate rather than delving into Database and JDBC specifics. It
drastically simplifies object persistence development.

Going this way you do not have to choose the database you are developping for.
The tool can also generate the database schema for you.

The final database choice decision comes upon deployment, providing you with a
maximum flexibility to your own requirements, your customers legacy, your ISPs
offering. You can move from Postgresql, MySql to HSQL (Pure Java DB) or Oracle
database (and many more).

Worth to mention is the large quantity and high quality of Hibernate
documentation, as well as its integration into ANT and XDoclet.

Hibernate websites:
http://hibernate.bluemars.net/
http://sourceforge.net/projects/hibernate

Hibernate articles:
http://www7b.software.ibm.com/dmdd/library/techarticle/0306bhogal/0306bhogal.html
http://www.meagle.com:8080/hibernate.jsp

Hibernate and XDoclet:
http://xdoclet.sourceforge.net/tags/hibernate-tags.html


I also heard about Torque but have no experience with it:

http://db.apache.org/torque/


Patrick



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to