This coherent with what is done for Table. All platform specific things
are grouped into an options array. Eventually flags should be migrated
into options as well.

Support for Partial Indexes was available in Doctrine 1 following
http://www.doctrine-project.org/jira/browse/DC-82. This commit
reintroduce support for Doctrine 2. We use the same syntax with an
optionnal "where" attribute for Index and UniqueConstraint.

- 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

- Fixing issue, key name corrected

[DBAL-166] Default MySQL to UTF8/utf8_general_ci. Allow to set default table options from SchemaConfig.

[DBAL-220] Add support for Index flags and implement support for SQL Server CLUSTERED/NONCLUSTERED and MySQL FULLTEXT.

[DBAL-204] Sane refactoring of the previous idea. Removed a bunch of code again and implemented proper schema namespacing. Also got the wording right (hopefully) and fixed the algorithms.

[DBAL-195] Fix AbstractSchemaManagertests/Doctrine/Tests/DBAL/Functional/Schema/SchemaManagerFunctionalTestCase.phpdropAndCreateSequence

[DBAL-195] Fix AbstractSchemaManagertests/Doctrine/Tests/DBAL/Functional/Schema/SchemaManagerFunctionalTestCase.phpdropAndCreateSequence

DBAL-88 - Change index retrieval of MySQL to use information_schema.statistics which avoids errors when using reserved words for table names (for example in database driver).

[DBAL-42] Add support to reverse engineer Comments from MySQL, PostgreSQL and ORacle into Doctrine\DBAL\Schema\Column instances and added comment comparison into Comparator.

DBAL-50 - Explicitly add an index for each foreign key added to a Schema\Table instance. Removed code to FixSchema based on foreign keys, since assumptions now dont apply anymore. Refactored algorithms to check for duplicate or potential overrule indexes into Schema\Index classes, added tests and unified Table API handling these conflicts

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