Fix behaviour of Connection::delete when an empty array of criteria is provided
#722 - avoiding unneeded variable overwrites, using ternary experssions instead
Merge branch 'hotfix/#722-connection-delete-with-empty-criteria'

Close #722
Exclude tables with table_type of VIEW

This excludes views registered by PostGIS 2.x like geography_columns, geometry_columns, raster_columns and raster_overviews.
The table_name != 'geometry_columns' is kept for PostGIS 1.5 compatibility. The type changed to VIEW in PostGIS 2.0.
Add functional test to ensure views are excluded by listTables()
Fixed undefined index notice when attempting to reconnect a MasterSlaveConnection after close has called
Merge pull request #726 from alekitto/ms_reconnect_notice

MasterSlaveConnection::close() should reset connections array
#722 - Implementing base `InvalidArgumentException` with simple static constructor
#722 - `Doctrine\DBAL\Connection#delete()` should refuse non-empty criteria
#722 - `Doctrine\DBAL\Connection#delete()` refuses non-empty criteria
#722 - basic coverage for `Doctrine\DBAL\Exception\InvalidArgumentException`
Merge pull request #727 from Ocramius/hotfix/#722-disallow-empty-delete-criteria

Disallow empty delete criteria on the connection
Merge pull request #725 from jsor/fix-list-table-sql-for-postgresql-with-postgis

Exclude tables with table_type of VIEW
Quote the name of an index in the create table statement.
#723 - Added tests