Due to variations in data types and SQL syntax, the following databases are currently supported:
| MySQL | No Issues |
| PostgreSQL | 8.2+ is required to use the “drop all database objects” functionality. |
| Oracle | 11g driver is required when using the diff tool on databases running with AL32UTF8 or AL16UTF16 |
| MS-SQL | No Issues |
| Sybase | ASE 12.0+ required. “select into” database option needs to be set. Best driver is JTDS. Sybase does not support transactions for DDL so rollbacks will not work on failures. Foreign keys can not be dropped which can break the rollback or dropAll functionality. |
| DB2 | No Issues. Will auto-call REORG when necessary. |
| Apache Derby | No Issues |
| HSQL | No Issues |
| H2 | No Issues |
| InterSystems Caché | No Issues |
| Firebird | No Issues |
| MaxDB / SAPDB | No Issues |
Since LiquiBase is built on top of standard JDBC, the only ties it has to the underlying database is through the SQL that can vary from DBMS to DBMS. If you attempt to use LiquiBase with an unsupported database, it will try to run and will most likely succeed. The only problem you are likely to run into is the current date/time function name. If LiquiBase is unable to determine the correct date/time function, you can pass it in via the currentDateTimeFunction argument (see command line and Ant).
You may also run into problem with the SQL generated by the change/refactoring tags on unsupported databases. The best way to deal with this problem is to first try the standard change/refactoring tags. If it generates an error, you can fall back to the <sql> tag to code whatever change you need to make in a way that your database understands.
If, for some reason, the DatabaseChangeLog table cannot be created on your database, the base creation SQL that you can modify to suite your needs is:
CREATE TABLE DATABASECHANGELOG (id varchar(150) NOT NULL, author varchar(150) NOT NULL, filename varchar(255) NOT NULL, dateExecuted datetime NOT NULL, md5sum varchar(32), description varchar(255), comments varchar(255), tag varchar(255), liquibase varchar(10), PRIMARY KEY(id, author, filename))
Reasons for creating the DatabaseChangeLog table yourself include database that require null fields to be specified as such and index limitations that don't allow primary keys on fields as long. You can change the data types and or data type lengths all you want, LiquiBase simply checks for the existence of the table.