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.

[DBAL-589] Fix type hint in Column::visit()

Demonstrates that NULL parameters are handled incorrectly by the sql parser utils as of 2.3.4

If allow_url_fopen isnt enabled, fopen will return false.

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