polotrack
polotrack copied to clipboard
Bump diesel from 0.15.2 to 1.4.6 in /backend
Bumps diesel from 0.15.2 to 1.4.6.
Release notes
Sourced from diesel's releases.
1.4.6
Fixed
- Fixed a use-after-free issue in the
QueryableByName
implementation of ourSqlite
backend- Updated several dependencies
1.4.5
Fixed
- Update several dependencies
- Fixed an issue where transactions that would fail to commit would leave the connection in a broken non-committed non-rolled-back state.
- Fix a bug that result in leaking sockets/file descriptors on failed connection attempts for postgresql
- Fix an incompatibility with newer
libmysqlclient
versions- Remove some potential harmful usages of
mem::uninitialized
1.4.4
Fixed
- Update several dependencies
- Fixed a bug with printing embedded migrations
As part of this release also updated versions of
migration_internals
andmigration_macros
are published.1.4.3
Fixed
- Updated several dependencies
- Fixed an issue where the postgresql backend exploits implementation defined behaviour
- Fixed issue where rustdoc failed to build the documentation
diesel_derives
anddiesel_migrations
are updated to syn 1.0v1.4.0
New Features
In contrast to the last release most changes in this release are minor or internal. We've added support for newer versions of some dependency crates (libsqlite-sys, uuid, ipnetwork).
Diesel CLI got a command line flag to check if a generated schema matches the already existing one. This is useful for CI setups to check there if the committed generated schema file matches the committed migrations.
We've added support for the
diesel_mange_updated_at('table_name')
SQL function on SQLite. This function handles the setup of an trigger that automatically updates theupdated_at
column on update operations.Additionally several helpers were added to support the deserialisation of tuples and composite types on PostgreSQL.
As always, a full list of changes can be found it in the changelog
Thanks
Thank you to everyone who helped make this release happen through bug reports, and discussion on Gitter. While we don't have a way to collect stats on that form of contribution, it's greatly appreciated.
... (truncated)
Changelog
Sourced from diesel's changelog.
[1.4.6] - 2021-03-05
Fixed
- Fixed a use-after-free issue in the
QueryableByName
implementation of ourSqlite
backend- Updated several dependencies
[1.4.5] - 2020-06-09
Fixed
- Update several dependencies
- Fixed an issue where transactions that would fail to commit would leave the connection in a broken non-committed non-rolled-back state.
- Fix a bug that result in leaking sockets/file descriptors on failed connection attempts for postgresql
- Fix an incompatibility with newer
libmysqlclient
versions- Remove some potential harmful usages of
mem::uninitialized
[1.4.4] - 2020-03-22
Fixed
- Update several dependencies
- Fixed a bug with printing embeded migrations
[1.4.3] - 2019-10-11
Fixed
- Updated several dependencies
- Fixed an issue where the postgresql backend exploits implementation defined behaviour
- Fixed issue where rustdoc failed to build the documentation
diesel_derives
anddiesel_migrations
are updated to syn 1.0[1.4.2] - 2019-03-19
Fixed
- Parenthesis are now inserted around all mathematical operations. This means that
(2.into_sql() + 3) * 4
will correctly evaluate to 20 as expected. Previously we would generate SQL that evaluated to 14. This could even result in runtime errors if multiple types were involved (for example,interval * (integer + 1)
)[1.4.1] - 2019-01-24
Fixed
... (truncated)
Commits
b0c8e99
Release diesel 1.4.6ae72835
Merge pull request #2663 from weiznich/bugfix/fix_use_after_freecead1a3
Downgrade max bigdecimal version as the new version is incompatible2a612f0
Run cargo fmtd699f14
Bump some dependenciesd219211
Address review commentsd413328
Fix a use-after-free bug in our Sqlite backend8e9e639
More fixes for mysql setup453cfb8
Remove clippy from ci on release branchd856d35
Fix mysql instalation on macos- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.