GOMODULES
/
pgx
mirror of https://github.com/jackc/pgx.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix some typos

pull/594/head
ferhat elmas 2019-09-04 12:46:50 +02:00
parent be8ed87408
commit 912b2fcc3a
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -12,7 +12,7 @@ proxies, load balancers, logical replication clients, etc.
## v4
This is the `v4` branch. `v4` is in release candate state but is not officially released.
This is the `v4` branch. `v4` is in release candidate state but is not officially released.
## Example Usage

4
batch.go
View File

@ -36,7 +36,7 @@ type BatchResults interface {
// QueryRow reads the results from the next query in the batch as if the query has been sent with Conn.QueryRow.
QueryRow() Row
// Close closes the batch operation. Any error that occured during a batch operation may have made it impossible to
// Close closes the batch operation. Any error that occurred during a batch operation may have made it impossible to
// resyncronize the connection with the server. In this case the underlying connection will have been closed.
Close() error
}
@ -95,7 +95,7 @@ func (br *batchResults) QueryRow() Row {
}
// Close closes the batch operation. Any error that occured during a batch operation may have made it impossible to
// Close closes the batch operation. Any error that occurred during a batch operation may have made it impossible to
// resyncronize the connection with the server. In this case the underlying connection will have been closed.
func (br *batchResults) Close() error {
if br.err != nil {

2
doc.go
View File

@ -154,7 +154,7 @@ pgx also includes support for custom types implementing the database/sql.Scanner
interfaces.
If pgx does cannot natively encode a type and that type is a renamed type (e.g. type MyTime time.Time) pgx will attempt
to encode the underlying type. While this is usually desired behavior it can produce suprising behavior if one the
to encode the underlying type. While this is usually desired behavior it can produce surprising behavior if one the
underlying type and the renamed type each implement database/sql interfaces and the other implements pgx interfaces. It
is recommended that this situation be avoided by implementing pgx interfaces on the renamed type.