Documentation section lists non obvious behaviours of DBAL component and ways to avoid them.
Consider using 'datetime' type for your columns instead of 'timestamp' as it gives you more unified support and ability to define proper default values.
Timestamp fields behaviour is different in MySQL 5.5 and MySQL 5.6+!
Not all drivers are implemented equally:
MySQL driver if fully supported by DBAL layer with all functionality being available.
Default table engine is set to InnoDB.
Postgres driver includes custom implementation of InsertQuery in order to address return value of
auto-incremental PK, it will automatically add RETURNING {primary key} to generated SQL query.
SQLServer includes fallback mechanism to limit your selection without orderBy specified. In some cases it might add additional _row_number_ column at the end of selected columns.
SQLServer is optimized to work with 12+ versions of Microsoft SQL Server.
SQLIte DBMS does not support set of table altering operations, in order to address some of schema migrations will be performed using temporary tables and data copy.