-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropped support of fetching objects and non-zero column #3070
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reported the AppVeyor build failure as appveyor/ci#2204. |
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
from
March 29, 2018 05:34
540002e
to
b1e9e7d
Compare
Ocramius
referenced
this pull request
Apr 4, 2018
morozov
force-pushed
the
develop
branch
3 times, most recently
from
April 9, 2018 15:30
fd275f8
to
c78e0e5
Compare
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
from
April 9, 2018 17:46
b1e9e7d
to
8870f08
Compare
morozov
force-pushed
the
develop
branch
2 times, most recently
from
June 6, 2018 21:46
72cddfb
to
d8f1786
Compare
morozov
force-pushed
the
develop
branch
3 times, most recently
from
July 2, 2018 00:52
67bd64c
to
7e5fb71
Compare
morozov
force-pushed
the
develop
branch
2 times, most recently
from
October 7, 2018 22:01
c4478a0
to
e5a586e
Compare
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
3 times, most recently
from
January 29, 2020 01:17
78263d5
to
be09d0f
Compare
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
from
March 14, 2020 20:09
be09d0f
to
5d91e02
Compare
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
3 times, most recently
from
April 13, 2020 06:13
86a0bb9
to
a21bfca
Compare
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`.
morozov
force-pushed
the
stmt-fetch-mode-args-cleanup
branch
from
April 13, 2020 06:22
a21bfca
to
aa6ae1d
Compare
greg0ire
approved these changes
Apr 13, 2020
4 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #3066 (comment) and #2958 (comment) for the source.
Summary:
FetchMode::STANDARD_OBJECT
andFetchMode::CUSTOM_OBJECT
are no longer supported.FetchMode::COLUMN
with a non-zero index is no longer supported.Connection::fetchColumn()
signature where the 3rd argument is now$types
, not$columnIndex
.Reasoning:
fetch()
andfetchAll()
in any of the non-PDO drivers and in the caching layer.$args
in fetch statement methods and therefore simplify the interface.