If you have a role "postgres" in PostgreSQL that is described like this:
```
-- Role: postgres
CREATE ROLE postgres LOGIN
  ENCRYPTED PASSWORD 'md53175bce1d3201d16594cebf9d7eb3f9d'
  SUPERUSER INHERIT CREATEDB CREATEROLE REPLICATION;
ALTER ROLE postgres IN DATABASE sf_test
  SET search_path = "$user", public, access, geographic, rrhh;
```

At the time when I execute the statement (Part of $schema value in the line 348):
```
SELECT string_to_array((select replace(replace(setting,"$user",user),' ','') from pg_catalog.pg_settings where name = 'search_path'),',')
```
I fetch this result:
```
{public," access"," geographic"," rrhh"}
```
Look the space character that is on the start of each string.This error does not match any namespace to which the role has access. This is critical when you have PostgreSQL database and you work with schemas.

If allow_url_fopen isnt enabled, fopen will return false.

Fixed a PHP warning in DBALException::driverExceptionDuringQuery() when a parameter contains binary data.

This reverts commit d7032199.

DBAL-54 was fixed in commit 3d55dc8e by
changing SQL queries order. However it was later reintroduced.

This patch uses a different, more future-proof way, approach by using
DROP SEQUENCE ... CASCADE syntax, and thus does not depend on queries order.

regex pattern does not support sql casting using :: operator for example select mydate::date from mytable;

Remove test for 2.3 branch