DBAL-39 - Changed SQLLogger again, the recent change disallows to log a failed query, however adding a lastexecuted query would add additional overhead (last params and types would be needed to). So now each logger has a startQuery() and a stopQuery() method. Additionally the logger now gets passed the array of types.

DBAL-37 - Fix PostgreSQL Platform not supporting changes in Autoicnrement during ALTER TABLE generation

DBAL-33 - Added flexible DateTime type that can be used as replacement when variable date/time parts are returned from the database, for example with PostgreSQL TIMESTAMP(n) and TIME(n) types

Fix for both DDC-710 and  DDC-693, added many tests for null conversion and additional tests for the empty value conversion

Apply array_change_key_case in MysqlSchemaManager::_getPortableColumnDefinition() and adapt further code to work with it

DBAL-26 - Fix nasty bug with null values in Date, DateTime, DateTimeTz and Time fields introduced with the DBAL-22 fix

DBAL-22 Change check for array and object values into strict false check instead of using is_array and is_object

DBAL-22 - Throw ConversionException if DateTime, Time, Date, DateTimeTz, Array or Object conversions from the Database to PHP fail

DBAL-11 - Changed Interface of SQLLogger to allow for timing variables, added tests for logging. Contract of Loggers changed, they are not called before the query but after the query they are logging, which means queries that fail wont appear in the logs.

DBAL-21 - Fallback for Domain Types to underyling db types when matching against Doctrine Mapping typesin Postgres Platform/SchemaManager

DBAL-22 - Make DateTime type the fallback for platforms not supporting DateTimeTz, add test for the later and test for default DateTimeZone

DBAL-22 - Fix DateTime with Timezone handling in Postgres and Oracle by introducing new type DateTimeTz and have SchemaManagers of both platforms detect this type. Added general conversion testcase which made some bugs in Oracle Date Handling and $stmt->fetchColumn() appear

Temporary fix for issues appearing due to DBAL-2 reopening, found an actual additional bug that is now fixed in PostgresSQL Schema Manager

Fix change to Postgresql NULL Column detection