Heiko Stoermer (08/31/1999 07:57):
here are my thoughts... (you wanted them :) ) I've been working with MySQL for the last 2 years now, and I pretty much liked it for the ease of use. (good PERL module, loads of tools). For our current project however, we switched to postgresql because we simply wanted to try it out. And I must say that I found postgresql no harder to use, especially the database grants are even easier to handle. It has many more functions (e.g. transactions), but I think if you are experienced in MySQL you will be able to work with postgresql within two days or so. Concerning Oracle, Informix etc.: I have no experiences with these, because for me they seem too bloated for web use. There was never even one reason to use a database that costs you $ 200,000 for unlimited web use ;) so I didn't even get in touch with them. There might be an alternative DB called "Adabas D" by the german Software AG, which seems to be right in the middle between freeware postgres and expensive Oracle concerning price and features. However, I'm not informed about DA status for Zope interaction. But you might want to check that out.
Hi, and thanks. I've same concerns regarding the big commercial DB's as you, so they are out of the question. The situation is that I actually don't have any experience with DB products other than MS Access, even though I'm a Linux freak :-) That means that I'll be starting from scratch in both cases (MySQL or PostgreSQL). If I can administer both DB's from within Zope, then I'll choose PGSQL because you say they're equally easy to work with an PGSQL has transaction control. Can I administer DB's from within Zope? PGSQL's advantage is transaction control and MySQL's would be tools and userbase, right? So which is it going to be? PGSQL or MySQL Best regards, Steen Suder