TimeType resets date fields (i.e. unused DateTime object fields) to UNIX
epoch (1970-01-01). This makes TIME field mapping stabe (i.e. same time
will be always mapped to the same DateTime fields).

See DDC-179 (similar issue with DateType). Fixes DBAL-993.

TimeType resets date fields (i.e. unused DateTime object fields) to UNIX
epoch (1970-01-01). This makes TIME field mapping stabe (i.e. same time
will be always mapped to the same DateTime fields).

See DDC-179 (similar issue with DateType). Fixes DBAL-993.

Changed to call platform specific Boolean conversion

The "decimal" mapping type does not map to float/double anymore:
https://github.com/doctrine/dbal/commit/9f51afa210d5c0165dfe6c622e07e42aa54c09fb#lib/Doctrine/DBAL/Types/DecimalType.php

Thank you.

- Fixed docblocks
- Removed return statements on void methods
- Cleaned up unused private / local variables
- Fixed license issues
- Removed SVN leftovers
- Fixed doctrine-project.org links
- Added line breaks before return statements

If allow_url_fopen isnt enabled, fopen will return false.

[DBAL-178] Fixed an undescriptive error message and a problem when using custom types and their reverse engineering from the database. Allows Type#getMappedDatabaseTypes() to be implemented in custom types, mapping to vendor database types during reverse engineering.

DDC-451 - GUID support through a specific GUID Type, SQL Server specific implementation all others fallback to Varchar fields, no automatic default value = new guid support yet.