Which out of MySQL or PostGres would work better with Zope? Which has the more stable DA and what one should I use in each case?
I'm running zope 2.2.2 (previous 2.1.6) with postgres/PoPy as a loginmanager backend for an extranet with 500 users. And zope 2.3.3 for a low traffic portal where all the content comes from postgres and is updated via foxpro/odbc by the client. Both run without any problem since about 10 months - the zopes were update since then. One minor thing with Zpopyda is that I'm not quite sure about which and how the different versions of postgres/popy/zpopy/zope will work together and so updating postgres on a server with multiple zopes using zpopyda could get a bit of a headache.
I like postgres very much, so I'm not neutral, but anyway, some advocacy might be in order. There's virtually no limitation of field sizes in postgres 7.1 btw (64 TB table size, 1GB field size, 1600 cols/table ;-) )
True. Then maybe the criteria for evaluation is features-vs-speed? I've always said that MySQL is a Ferrari, and PostgreSQL like a big Mack truck. One will get you there reeeeeeally fast; and the other will let you take your house along for the ride. If you need stored procs or anything beyond basic, stripped-down SQL, then PostgreSQL is probably the winner in that evaluation. BUT, if you need speed, speed speed and don't need all the bells and whistles, MySQL simply cannot be beat. I have seen db-driven wesites with 10+ million visitors daily run on MySQL, and I am fairly certain that the same setup on PostgreSQL would require a few more boxen -;^>=
(kinda OT for Zope, but which has the better full-text search capability?)
Do you mean fast or flexible?
100% correct! See my previous paragraph. I like both, currently using both on different projects. Sometimes a screwdriver will do the job, and sometimes I need the whole #$@* toolbox. And if anyone disagrees, please do so - I've been saying this forever, and that means that my opinion may be a little stale!