- 02 Jul, 2020 2 commits
-
-
Sergei Morozov authored
-
Sergei Morozov authored
-
- 13 Apr, 2020 1 commit
-
-
Sergei Morozov authored
1. `FetchMode::STANDARD_OBJECT` and `FetchMode::CUSTOM_OBJECT` are no longer supported. 2. `FetchMode::COLUMN` with a non-zero index is no longer supported. 3. Incompatible change in the `Connection::fetchColumn()` signature where the 3rd argument is now `$types`, not `$columnIndex`.
-
- 08 Apr, 2020 1 commit
-
-
Sergei Morozov authored
-
- 21 Mar, 2020 3 commits
-
-
Sergei Morozov authored
-
Sergei Morozov authored
-
Sergei Morozov authored
-
- 10 Mar, 2020 1 commit
-
-
Craig Duncan authored
-
- 30 Dec, 2019 1 commit
-
-
Sergei Morozov authored
-
- 26 Aug, 2019 1 commit
-
-
Bas Peeters authored
-
- 30 May, 2019 1 commit
-
-
Sergei Morozov authored
-
- 26 Feb, 2019 1 commit
-
-
Sergei Morozov authored
-
- 03 Feb, 2019 1 commit
-
-
Sergei Morozov authored
-
- 28 Sep, 2018 2 commits
-
-
Sergei Morozov authored
-
Sergei Morozov authored
-
- 29 Jan, 2018 1 commit
-
-
Sergei Morozov authored
-
- 12 Jul, 2016 1 commit
-
-
Christopher Davis authored
-
- 11 Jul, 2016 1 commit
-
-
Christopher Davis authored
-
- 09 Jul, 2016 1 commit
-
-
Christopher Davis authored
So they get passed to the SQLLogger on `Statement::execute`.
-
- 30 Jun, 2016 1 commit
-
-
Steve Müller authored
-
- 17 Oct, 2015 1 commit
-
-
Tobias Schultze authored
-
- 06 Apr, 2015 1 commit
-
-
Darien Hager authored
Add a unit-test to verify that when statements throw exceptions, the logger still has stopQuery called.
-
- 16 Sep, 2012 3 commits
-
-
Rob Apodaca authored
-
Rob Apodaca authored
-
Rob Apodaca authored
When parameters are passed to Doctrine\DBAL\Statement::execute, they are not passed to any enabled logger(s).
-