So they get passed to the SQLLogger on `Statement::execute`.

- 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

When parameters are passed to Doctrine\DBAL\Statement::execute, they are not passed to any enabled logger(s).

bindParam function expects length parameter for oci_bind_by_name oci8

This reverts commit 17a265d9.

driver function

Fix Statement class passing bound parameter objects to SQL logger without type information: save parameter's converted value

This enables a more natural way of interacting with result sets,
and re-introduces in Doctrine DBAL a feature that has been available
in PDO from the begining.

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-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.

[2.0][DDC-354][DDC-425] Fixed. Encapsulated SQL logging better in the DBAL. Added binding types to DBAL mapping types as well as using these binding types in the persisters. Query and NativeQuery now support PDO binding types as well as DBAL mapping types when binding parameters.

[2.0] Implemented DQL bulk DELETE support for Class Table Inheritance. Other cleanups, refactorings and docblock additions.