Berkeley no longer the assumed default database
This is an archived entry from the Movable Type 3.2 beta test.
Entries from the current beta release (v3.3) can be found here.
In previous versions of Movable Type, the Berkeley DB option was assumed to be the default if SQL information was not specified in the configuration file. If SQL information was provided, then Movable Type would simply ignore the DataSource setting (even if it was uncommented in the config file), and use SQL instead.
We've now made a change which will force the user to specifically indicate which database option they want to use, rather than relying on a default assumption of BerkeleyDB. But an unresolved bug related to this change could pose some problems for those upgraders who still have an uncommented DataSource setting in their configuration file, as Movable Type may try to incorrectly use it during the upgrade process.
So, if you're using SQL, please check your configuration file before upgrading to make sure that the DataSource setting is commented out (by placing a # at the beginning of the line).
Otherwise, if the path specified for DataSource no longer exists, you'll probably get an error about it during the upgrade. If the DataSource path does still exist, Movable Type could inadvertently upgrade older database files which you're no longer using.
Posted on July 22, 2005 7:39 AM in Announcements
Comments