- 03 Jan, 2015 3 commits
-
-
Terje Bråten authored
-
Terje Bråten authored
-
Steve Müller authored
Backporting a fix to allow connection without dbname
-
- 01 Jan, 2015 2 commits
-
-
Marco Pivetta authored
-
Steve Müller authored
-
- 31 Dec, 2014 2 commits
-
-
Steve Müller authored
-
Claudio Zizza authored
-
- 27 Dec, 2014 2 commits
-
-
Marco Pivetta authored
-
Steve Müller authored
-
- 26 Dec, 2014 4 commits
-
-
Claudio Zizza authored
-
Claudio Zizza authored
-
Claudio Zizza authored
-
Claudio Zizza authored
-
- 31 Oct, 2014 1 commit
-
-
mike authored
The fix is already in master at https://github.com/doctrine/dbal/commit/387eb5457498781e24716286a2511f5d030d63fb but because it has not been backported the functionnality is still broken for symfony 2.5 for instance.
-
- 16 Oct, 2014 4 commits
-
-
Marco Pivetta authored
-
Marco Pivetta authored
-
Marco Pivetta authored
Cherry pick to 2.4: [DBAL-717] Fix bug in MasterSlaveConnection with keepSlave option and switch back after transaction.
-
Benjamin Eberlei authored
[DBAL-717] Fix bug in MasterSlaveConnection with keepSlave option and switch back after transaction. Conflicts: tests/Doctrine/Tests/DBAL/Functional/MasterSlaveConnectionTest.php
-
- 20 Aug, 2014 2 commits
-
-
Guilherme Blanco authored
[DDC-2310] [2.4] Fix evaluation of NOLOCK table hint on SQL Server
-
Steve Müller authored
(cherry picked from commit 69931faa)
-
- 04 Aug, 2014 2 commits
-
-
Marco Pivetta authored
Add close() method in MasterSlaveConnection.php
-
Chuck authored
-
- 29 Jul, 2014 3 commits
-
-
Marco Pivetta authored
-
Marco Pivetta authored
-
Sergey Zhuravel authored
-
- 27 Jul, 2014 2 commits
-
-
Marco Pivetta authored
Remove duplicate suggest section in composer.json
-
jeroendedauw authored
-
- 23 Jul, 2014 2 commits
-
-
Sergey Zhuravel authored
-
Sergey Zhuravel authored
-
- 22 Jul, 2014 1 commit
-
-
Sergey Zhuravel authored
-
- 08 Feb, 2014 5 commits
-
-
Benjamin Eberlei authored
-
Bart Visscher authored
-
Bart Visscher authored
-
Benjamin Eberlei authored
-
Steve Müller authored
-
- 05 Jan, 2014 2 commits
-
-
Benjamin Eberlei authored
-
José Gabriel González Pérez authored
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.
-
- 03 Jan, 2014 3 commits
-
-
Benjamin Eberlei authored
-
Steve Müller authored
-
Benjamin Eberlei authored
-