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

Update CHANGELOG

non-blocking
Jack Christensen 2022-04-16 14:14:59 -05:00
parent e94cf1fbaa
commit 1c90746cf5
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CHANGELOG.md
View File

@ -33,7 +33,7 @@ generally defined by implementing an interface that a particular `Codec` underst
All array types are now handled by `ArrayCodec` instead of using code generation for each new array type. This All array types are now handled by `ArrayCodec` instead of using code generation for each new array type. This
significantly reduced the amount of code and the compiled binary size. This also means that less common array types such significantly reduced the amount of code and the compiled binary size. This also means that less common array types such
as `point[]` are now supported. as `point[]` are now supported. `Array[T]` supports PostgreSQL multi-dimensional arrays.
### Composite Types ### Composite Types
@ -42,8 +42,8 @@ values, but any type may now implement `CompositeIndexGetter` and `CompositeInde
### Range Types ### Range Types
Range types are now handled with generic types `RangeCodec[T]` and `Range[T]`. This allows additional user defined range Range types are now handled with types `RangeCodec` and `Range[T]`. This allows additional user defined range types to
types to easily be handled. easily be handled.
### pgxtype ### pgxtype
@ -70,6 +70,9 @@ only `string` is handled. This is to allow the possibility of future binary supp
considering `[]byte` to be binary format and `string` text format. This change should have no effect for any use with considering `[]byte` to be binary format and `string` text format. This change should have no effect for any use with
`pgx`. The previous behavior was only necessary for `lib/pq` compatibility. `pgx`. The previous behavior was only necessary for `lib/pq` compatibility.
Added `*Map.SQLScanner` to create a `sql.Scanner` for types such as `[]int32` and `Range[T]` that do not implement
`sql.Scanner` directly.
### Number Type Fields Include Bit size ### Number Type Fields Include Bit size
`Int2`, `Int4`, `Int8`, `Float4`, `Float8`, and `Uint32` fields now include bit size. e.g. `Int` is renamed to `Int64`. `Int2`, `Int4`, `Int8`, `Float4`, `Float8`, and `Uint32` fields now include bit size. e.g. `Int` is renamed to `Int64`.
@ -95,6 +98,10 @@ This matches the convention set by `database/sql`. In addition, for comparable t
* Renamed `pgtype.None` to `pgtype.Finite`. * Renamed `pgtype.None` to `pgtype.Finite`.
* `RegisterType` now accepts a `*Type` instead of `Type`. * `RegisterType` now accepts a `*Type` instead of `Type`.
## stdlib
* Removed `AcquireConn` and `ReleaseConn` as that functionality has been built in since Go 1.13.
## Reduced Memory Usage by Reusing Read Buffers ## Reduced Memory Usage by Reusing Read Buffers
Previously, the connection read buffer would allocate large chunks of memory and never reuse them. This allowed Previously, the connection read buffer would allocate large chunks of memory and never reuse them. This allowed