[Zope] A Suitable RDBMS?

[Ragnar Beer]

>Yeah that was probably me, not to slam MySQL, it's fast, it's free, and
>it's stable.  It's lack of transactions however means that you have to
>be aware of and live with the possibilty of inconsistent states of data
>between MySQL and Zope.
>
>For read only operations, or low-write, or if an external application
>handles inserting your data and Zope only reads it, this is not really a
>problem.  Also, it's only really manifest if you change the database and
>then change something in Zope and an error occours.  If you can isolate
>your SQL calls as much as possible, then this shouldn't be a problem.
>
>-Michel

Fortunately MySQL has transactions high up on the todo list (but it's 
already been there for QUITE A WHILE).

-Ragnar