sqlx/CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.2.6 - 2020-03-10

Added

• [#114] Export sqlx_core::Transaction [@thedodd]

Fixed

• [#125] [#126] Fix statement execution in MySQL if it contains NULL statement values [@repnop]

• [#105] [#109] Allow trailing commas in query macros [@timmythetiny]

0.2.5 - 2020-02-01

Fixed

• Fix decoding of Rows containing NULLs in Postgres #104

• After a large review and some battle testing by @ianthetechie of the Pool, a live leaking issue was found. This has now been fixed by @abonander in #84 which included refactoring to make the pool internals less brittle (using RAII instead of manual work is one example) and to help any future contributors when changing the pool internals.

• Passwords are now being precent decoding before being presented to the server [@repnop]

• [@100] Fix FLOAT and DOUBLE decoding in MySQL

Added

• [#72] Add PgTypeInfo::with_oid to allow simple construction of PgTypeInfo which enables HasSqlType to be implemented by downstream consumers of SQLx [@jplatte]

• [#96] Add support for returning columns from query! with a name of a rust keyword by using raw identifiers [@yaahc]

• [#71] Implement derives for Encode and Decode. This is the first step to supporting custom types in SQLx. [@Freax13]

0.2.4 - 2020-01-18

Fixed

• Fix decoding of Rows containing NULLs in MySQL (and add an integration test so this doesn't break again)

0.2.3 - 2020-01-18

Fixed

• Fix query! when used on a query that does not return results

0.2.2 - 2020-01-16

Added

• [#57] Add support for unsigned integers and binary types in query! for MySQL [@mehcode]

Fixed

• Fix stall when requesting TLS from a Postgres server that explicitly does not support TLS (such as postgres running inside docker) [@abonander]

• [#66] Declare used features for tokio in sqlx-macros explicitly

0.2.1 - 2020-01-16

Fixed

• [#64, #65] Fix decoding of Rows containing NULLs in MySQL [@danielakhterov]

• [#55] Use a shared tokio runtime for the query! macro compile-time execution (under the runtime-tokio feature) [@udoprog]

0.2.0 - 2020-01-15

Fixed

• https://github.com/launchbadge/sqlx/issues/47

Added

• Support Tokio through an optional runtime-tokio feature.

• Support SQL transactions. You may now use the begin() function on Pool or Connection to start a new SQL transaction. This returns sqlx::Transaction which will ROLLBACK on Drop or can be explicitly COMMIT using commit().

• Support TLS connections.

0.1.4 - 2020-01-11

Fixed

• https://github.com/launchbadge/sqlx/issues/43

• https://github.com/launchbadge/sqlx/issues/40

Added

• Support for SCRAM-SHA-256 authentication in Postgres #37 @danielakhterov

• Implement Debug for Pool #42 @prettynatty

0.1.3 - 2020-01-06

Fixed

• https://github.com/launchbadge/sqlx/issues/30

0.1.2 - 2020-01-03

Added

• Support for Authentication in MySQL 5+ including the newer authentication schemes now default in MySQL 8: mysql_native_password, sha256_password, and caching_sha2_password.

• Chrono support for MySQL was only partially implemented (was missing NaiveTime and DateTime<Utc>).

• Vec<u8> (and [u8]) support for MySQL (BLOB) and Postgres (BYTEA).