Changes to the List of Supported Databases
See System Requirements for current database support.
MT5
SQLite & PostgreSQL no longer supported in MT core.
To speed up development and quality-assurance testing, core support for SQLite and PostgreSQL have been dropped.
Note: If needed, the plugin architecture since MT4.0 supports the ability to create a database drivers for these databases. The Enterprise Pack has an example of this as it provides Oracle database support.
MT4
We have made a significant number of improvements to Movable Type’s database access layer that requires the use of SQL statements found only in later versions of MySQL. For that reason, the following databases are no longer supported:
- Berkeley DB
MySQL 3.x and older
MySQL 4.0 users should upgrade to MySQL 4.1 or greater
While we support MySQL 4.0 we recommend that users upgrade to a newer version of MySQL for the following reasons:
- MySQL 4.0 is not officially supported by the manufacturer.
- There are many database and SQL optimizations found in MySQL 4.1 which are utilized in Movable Type 4+.
phaoost on April 3, 2010, 6:27 a.m. Reply
dropping postgresql is a sad news
Alvar on April 6, 2010, 4:22 p.m. Reply
OMG, who had the stupid idea, to remove PostgreSQL-Support?
The same “developer”, who doesn’t like the use of transactions?
james2vegas on April 20, 2010, 7:18 p.m. Reply
Yeah, seriously PostgreSQL support in MT 5 will likely be a significant blocker for upgrades. Interestingly enough the distribution still has
/lib/MT/ObjectDriver/{DDL,SQL,Driver}/Pg.pm
I haven’t tested whether they work with the rest of the code, but they are not complicated modules and should be relatively easy to maintain (about 300 LOC), especially considering that Oracle and MSSQL are supported and they are closer to PostgreSQL than they are MySQL.
Especially amusing about this decision was its timing relative to the whole MySQL being sold to Oracle business, making non-MySQL databases more attractive.
bithive on May 13, 2010, 11:10 a.m. Reply
This is a huge disappointment. Not to mention it hurts my brain to imagine why an open source project written in Perl and using DBI would only support DBD::MySQL and not DBD::Pg too.
https://me.yahoo.com/failkraken#d0230 on July 1, 2010, 8:07 p.m. Reply
Heh. Yeah, it is always best to focus one’s development effort by solely supporting a “database” that silently truncates data.
‘Cause, you know, who cares if all the data makes it into the store? That’s the application layer’s job, right?
Remember: don’t assume data integrity with MySQL unless you’ve taken pains to set up MySQL properly by ignoring the defaults.
PRO IT Service on January 20, 2011, 7:45 a.m. Reply
If you are running based on BerkeleyDB, I would be pleased to work with you on converting your database to mySQL.
This includes converting damaged Berkeley databases. For instance those compromised databases where you cannot login to movable type anymore.
Kind Regards,
Mihai Bocsaru
Daily Movable Type Consultant
Web Development - Movable Type Consulting - Six Apart Partner
http://www.pro-it-service.com/
Movable Type Demo
http://www.movabletypedemo.org/