Naveen: In general I prefer PostgreSQL to MySQL, but it depends on what you're doing.
> 1) Entire installation will be on Windows > Licensing issues (cygwin reqmt for > postgre...) I do think you need cygwin on Windows to run PostgreSQL (in fact Cygwin comes with a pre-built postgresql) but I do not know the licensing requirements for Cygwin. > 2) Performance MySQL sometimes performs better, because it does less stuff. (Weaker SQL support, no transactions by default.) > 4) Store 40MB of Blobs - inline/offline BFILE kind > of support PostgreSQL has pretty spiffy large-object support. I don't know about MySQL's. PostgreSQL has an OID type, similar to Oracle LOB/CLOB, where you store just the object identifier in the row and the actual object data gets stored somewhere outside the table. They provide a set of stored procedures (lo_...) that allow you to import/export content from the filesystem, and I believe you can also create references to offline objects in the filesystem like Oracle BFILEs (not sure about this). The only catch is it doesn't work very well with Torque; especially if you want your Java code to be db-independent. When you do a "select oid_column from table" the PostgreSQL JDBC driver will return to you a java.lang.Integer containing the object ID number, not a java.sql.Blob. > 5) Transaction suport If transaction support is an absolute requirement, I'd go with PostgreSQL over MySQL. MySQL hasn't even supported transactions until somewhat recently and they're still treated as somewhat of an optional add-on rather than a core feature. > 7) Failover/Replication support This is something you won't really get with a free db though there might be a way to do it. -- Bill -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
