Skip to content

docs: correct reason to name prepared statements for pg #122

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

Merged
merged 1 commit into from
Jan 29, 2020
Merged

docs: correct reason to name prepared statements for pg #122

merged 1 commit into from
Jan 29, 2020

Conversation

charmander
Copy link
Contributor

pg has only ever had true parameterized queries.

pg has only ever had true parameterized queries.
@codecov
Copy link

codecov bot commented Dec 5, 2019

Codecov Report

Merging #122 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #122   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           1      1           
  Lines          36     36           
  Branches        6      6           
=====================================
  Hits           36     36

@felixfbecker felixfbecker changed the title Correct reason to name prepared statements for pg docs: correct reason to name prepared statements for pg Jan 29, 2020
@felixfbecker felixfbecker merged commit 7e6cad0 into felixfbecker:master Jan 29, 2020
@charmander charmander deleted the patch-1 branch January 29, 2020 08:58
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.

2 participants