Update to Metrics 2.0

This patch was authored and released by @tanner0101.

Updates to SwiftMetrics 2.0 which adds a new case the TimeUnit enum (#88, fixes #87)

Send terminate message on close

This patch was authored and released by @tanner0101.

A postgres terminate (X) message is now sent before the connection closes (#86, fixes #84).

Release Candidate 1

Updates to Swift 5.2 and macOS 10.15. Replaces CMD5 module with SwiftCrypto.

Release candidates represent the final shift toward focusing on bug fixes and documentation. Breaking changes will only be accepted for critical issues. We expect a final release of this package shortly after Swift 5.2's release date.

Support Swift.Set

Adds support for converting Swift.Set to / from a native Postgres array.

Handle NAME Type in PropertyData.string Property

Allows data that is contained as the .name type to be accessed through the PostgresData.string property.

var buffer = ByteBufferAllocator().buffer(capacity: 13)
buffer.writeString("password_hash")

let data = PostgresData(.name, value: buffer)
let string = data.string

// string == "password_hash"

char(n) (BPCHAR) length fix

The char(n) (BPCHAR) data type now correctly supports values longer than one byte when converting to fixed-width integers or strings (fixes #71, fixes #79, #72).

Fix Numeric String Serialization

Fixes a bug causing NUMERIC string serialization to produce incorrect values when numbers have more than 4 zeroes before or after the decimal place. (#78, fixes #77)

add PostgresData+JSON support

Adds new methods and properties for using the JSON data type. These methods mirror the existing methods for JSONB.

User-defined Enum + Optional Fix

Bound optional values that are nil should no longer result in an unexpected type warning (fixes #74)

PostgresData will now return strings correctly for user-defined types like enums.

Remove BPCHAR to Swift Integer conversion

Removes support for converting PostgresData containing BPCHAR bytes (CHARACTER(n), CHAR, etc) to Swift integers. Postgres CHAR(n) fields may be padded with extra zero-bytes which makes conversion tricky. Since Postgres intends CHARACTER fields to store string values, PostgresData should only support conversion to Swift strings. To store 8-bits natively, use Postgres "char" type (note the quotes).