2.3 KiB
2.3 KiB
Change Log
Unreleased
v0.4.0-rc.2 - 2019-05-03
Fixed
- Fixed Cargo features to actually enable the functionality they claim to.
v0.4.0-rc.1 - 2019-05-03
Changed
- The client API has been significantly overhauled. It now resembles
hyper
's, with separateConnection
andClient
objects. See the crate-level documentation for more details. - Connection string configuration now fully mirrors libpq's syntax, and supports both URL-style and key-value style strings.
- The TLS connection mode (e.g.
prefer
) is now part of the connection configuration rather than being passed in separately. - The Cargo features enabling
ToSql
andFromSql
implementations for external crates are now versioned. For example,with-uuid
is nowwith-uuid-0_7
. This enables us to add support for new major versions of the crates in parallel without breaking backwards compatibility. - Upgraded from
tokio-core
totokio
.
Added
FromSql
implementations can now borrow from the data buffer. In particular, this means that you can deserialize values as&str
. TheFromSqlOwned
trait can be used as a bound to restrict code to deserializing owned values.- Added support for channel binding with SCRAM authentication.
- Added multi-host support in connection configuration.
- The client now supports query pipelining, which can be used as a latency hiding measure.
- While the crate uses
tokio
by default, the base API can be used with any asynchronous stream type on any reactor. - Added support for simple query requests returning row data.
Removed
- The
with-openssl
feature has been removed. Use thetokio-postgres-openssl
crate instead. - The
with-rustc_serialize
andwith-time
features have been removed. Useserde
andSystemTime
orchrono
instead.
Older
Look at the release tags for information about older releases.