Update ecto_sql: 3.4.5 → 3.5.0 (minor)

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ ecto_sql (3.4.5 → 3.5.0) · Repo · Changelog

Release Notes

3.5.0 (from changelog)

Enhancements

[migrations] Add option to skip schema migrations table checks

[migrations] Add :migration_repo configuration to allow a different repository to host the schema migrations

[migrations] Support validate: false on references and constraints

[migrations] Accept :migration_primary_key as false and add :migration_foreign_key repo config

[postgres] Support for :identity key types in Postgres 10 or later

[postgres] Use IF NOT EXIST when creating index with create_if_not_exists, this requires PG 9.5+ or later

[repo] Support Repo.explain(:all | :update_all | :delete_all, query) for Ecto adapters

[sandbox] Allow for dynamic repos to be checked out in sandbox

Bug fixes

[migrations] Flush migration commands before executing before_commit callback

[migrations] Do not swallow errors when migration lock is disabled

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ ecto (indirect, 3.4.6 → 3.5.0) · Repo · Changelog

Release Notes

3.5.0 (from changelog)

v3.5 requires Elixir v1.8+.

Bug fixes

[Ecto.Changeset] Ensure :empty_values in cast/4 does not automatically propagate to following cast calls. If you want a given set of :empty_values to apply to all cast/4 calls, change the value stored in changeset.empty_values instead

[Ecto.Changeset] Do not force repository updates to happen when using optimistic_lock

[Ecto.Changeset] Do not automatically share empty values across cast/3 calls

[Ecto.Query] Consider query prefix in cte/combination query cache

[Ecto.Query] Allow the entry to be marked as nil when using left join with subqueries

[Ecto.Query] Support subqueries inside dynamic expressions

[Ecto.Repo] Fix preloading when using dynamic repos and the sandbox in automatic mode

[Ecto.Repo] Do not duplicate collections when associations are preloaded for repeated elements

Enhancements

[Ecto.Enum] Add Ecto.Enum as a custom parameterized type

[Ecto.Query] Allow :prefix in from to be set to nil

[Ecto.Query] Do not restrict subqueries in where to map/struct types

[Ecto.Query] Allow atoms in query without interpolation in order to support Ecto.Enum

[Ecto.Schema] Do not validate uniqueness if there is a prior error on the field

[Ecto.Schema] Allow redact: true in field

[Ecto.Schema] Support parameterized types via Ecto.ParameterizedType

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

distributeaid / toolbox