Skip to content
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

Merge 2.13.x into 3.1.x #4674

Merged
merged 5 commits into from Jun 17, 2021
Merged

Merge 2.13.x into 3.1.x #4674

merged 5 commits into from Jun 17, 2021

Conversation

derrabus
Copy link
Contributor

@derrabus derrabus commented Jun 17, 2021

Q A
Type improvement
BC Break no
Fixed issues N/A

This PR merges my docs changes up to the 3.1.x branch.

Sephster and others added 5 commits Jun 16, 2021
The example executes the function `fetchAllAssociative` on the Statement object but this object doesn't have this function. Instead, the function should be executed on the returned result set.
The existing example proposes clear-text storage of passwords, which is highly discouraged. Furthermore, such an example sheds a negative light on the Doctrine project if security-conscious developers evaluate whether they should use the library based on the provided examples.
Document a non-deprecated way to interact with prepared statements
@greg0ire greg0ire merged commit e817657 into doctrine:3.1.x Jun 17, 2021
48 checks passed
@greg0ire
Copy link
Member

@greg0ire greg0ire commented Jun 17, 2021

Thanks @derrabus !

@derrabus derrabus deleted the merge/2.13.x branch Jun 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants