All Versions
62
Latest Version
Avg Release Cycle
34 days
Latest Release
523 days ago
Changelog History
Page 4
Changelog History
Page 4
-
v3.4.2 Changes
April 10, 2020โจ Enhancements
- [Ecto.Changeset] Support multiple fields in
unique_constraint/3
- [Ecto.Changeset] Support multiple fields in
-
v3.4.1 Changes
April 08, 2020โจ Enhancements
- [Ecto] Add
Ecto.embedded_load/3
andEcto.embedded_dump/2
- [Ecto.Query] Improve error message on invalid JSON expressions
- [Ecto.Repo] Emit
[:ecto, :repo, :init]
telemetry event upon Repo init
๐ Bug fixes
- [Ecto.Query] Do not support JSON selectors on
type/2
๐ Deprecations
- [Ecto.Repo] Deprecate
conflict_target: {:constraint, _}
. It is a discouraged approach and{:unsafe_fragment, _}
is still available if someone definitely needs it
- [Ecto] Add
-
v3.4.0 Changes
March 24, 2020v3.4 requires Elixir v1.7+.
โจ Enhancements
- [Ecto.Query] Allow dynamic queries in CTE and improve error message
- [Ecto.Query] Add
Ecto.Query.API.json_extract_path/2
and JSON path support to query syntax. For example,posts.metadata["tags"][0]["name"]
will return the name of the first tag stored in the:map
metadata field - [Ecto.Repo] Add new
default_options/1
callback to repository - [Ecto.Repo] Support passing
:telemetry_options
to repository operations
๐ Bug fixes
- [Ecto.Changeset] Properly add validation annotation to
validate_acceptance
- [Ecto.Query] Raise if there is loaded non-empty association data without related key when preloading. This typically means not all fields have been loaded in a query
- [Ecto.Schema] Show meaningful error in case
schema
is invoked twice in anEcto.Schema
-
v3.3.4 Changes
February 27, 2020๐ Bug fixes
- [mix ecto] Do not rely on map ordering when parsing repos
- [mix ecto.gen.repo] Improve error message when a repo is not given
-
v3.3.3 Changes
February 14, 2020โจ Enhancements
- [Ecto.Query] Support fragments in
lock
- [Ecto.Query] Handle
nil
inselect_merge
with similar semantics to SQL databases (i.e. it simply returnsnil
itself)
- [Ecto.Query] Support fragments in
-
v3.3.2 Changes
January 28, 2020โจ Enhancements
- [Ecto.Changeset] Only bump optimistic lock in case of success
- [Ecto.Query] Allow macros in Ecto window expressions
- [Ecto.Schema] Support
:join_defaults
onmany_to_many
associations - [Ecto.Schema] Allow MFargs to be given to association
:defaults
- [Ecto.Type] Add
Ecto.Type.embedded_load
andEcto.Type.embedded_dump
๐ Bug fixes
- [Ecto.Repo] Ignore empty hostname when parsing database url (Elixir v1.10 support)
- [Ecto.Repo] Rewrite combinations on Repo.exists? queries
- [Ecto.Schema] Respect child
@schema_prefix
incast_assoc
- [mix ecto.gen.repo] Use
config_path
when writing new config inmix ecto.gen.repo
-
v3.3.1 Changes
December 27, 2019โจ Enhancements
- [Ecto.Query.WindowAPI] Support
filter/2
๐ Bug fixes
- [Ecto.Query.API] Fix
coalesce/2
usage with mixed types
- [Ecto.Query.WindowAPI] Support
-
v3.3.0 Changes
December 11, 2019โจ Enhancements
- [Ecto.Adapter] Add
storage_status/1
callback toEcto.Adapters.Storage
behaviour - [Ecto.Changeset] Add
Ecto.Changeset.apply_action!/2
- [Ecto.Changeset] Remove actions restriction in
Ecto.Changeset.apply_action/2
- [Ecto.Repo] Introduce
c:Ecto.Repo.aggregate/2
- [Ecto.Repo] Support
{:replace_all_except, fields}
in:on_conflict
๐ Bug fixes
- [Ecto.Query] Make sure the
:prefix
option in:from
/:join
also cascades to subqueries - [Ecto.Query] Make sure the
:prefix
option in:join
also cascades to queries - [Ecto.Query] Use database returned values for literals. Previous Ecto versions knew literals from queries should not be discarded for combinations but, even if they were not discarded, we would ignore the values returned by the database
- [Ecto.Repo] Do not wrap schema operations in a transaction if already inside a transaction. We have also removed the private option called
:skip_transaction
๐ Deprecations
- [Ecto.Repo]
:replace_all_except_primary_keys
is deprecated in favor of{:replace_all_except, fields}
in:on_conflict
- [Ecto.Adapter] Add
-
v3.2.5 Changes
November 03, 2019๐ Bug fixes
- [Ecto.Query] Fix a bug where executing some queries would leak the
{:maybe, ...}
type
- [Ecto.Query] Fix a bug where executing some queries would leak the
-
v3.2.4 Changes
November 02, 2019๐ Bug fixes
- [Ecto.Query] Improve error message on invalid join binding
- [Ecto.Query] Make sure the
:prefix
option in:join
also applies to through associations - [Ecto.Query] Invoke custom type when loading aggregations from the database (but fallback to database value if it can't be cast)
- [mix ecto.gen.repo] Support Elixir v1.9 style configs