Packages

ecto_adapters_dynamodb

3.4.1
3.6.1 3.6.0 3.5.0 3.4.1 3.4.0 3.3.7 3.3.6 3.3.5 3.3.4 3.3.3 3.3.2 3.3.1 3.3.0 3.2.0 3.1.3 3.1.2 3.1.1 3.1.0 3.0.3 3.0.2 3.0.1 3.0.0 2.0.4 2.0.3 2.0.2 2.0.1 2.0.0 2.0.0-beta.1 2.0.0-beta.0 2.0.0-alpha.4 2.0.0-alpha.3 2.0.0-alpha.2 2.0.0-alpha.1 2.0.0-alpha.0 1.3.0 1.2.1 1.2.0 1.1.3 0.5.1 0.5.0 0.4.6 0.4.5 0.4.4 0.4.3 0.4.2 0.4.1 0.4.0 0.3.0 0.2.3 0.2.2 0.2.1 0.1.2 0.1.1

A DynamoDB adapter for Ecto supporting basic queries. See https://github.com/circles-learning-labs/ecto_adapters_dynamodb for detailed instructions.

HexDocs

Current section

Files

Jump to
Readme
53 Versions
5 Dependencies
Dependants
Files
Activity
ecto_adapters_dynamodb CHANGELOG.md
Raw

CHANGELOG.md 

# Changelog for Ecto.Adapters.DynamoDB v3.x.x



[v2.x.x -> v3.x.x upgrade guide](/upgrade_guides/version_3_upgrade_guide.md)



## v3.4.1



- Update minimum Elixir to 1.13, update supported version to 1.17

- Fix warnings on Elixir 1.17

- Fix previously compile-time only config for maximum retry count to be runtime configurable



## v3.4.0



- Support for Ecto 3.11 (note that this breaks support for earlier versions of Ecto).

- Increase minimum Elixir version to 1.11



## v3.3.7



- Add retries to `insert`, `update` and `delete` when a transaction conflict occurs. Default

  retry count is 10 but may be configured with `:max_transaction_conflict_retries`



## v3.3.6



- Make `Ecto.Adapters.DynamoDB.decode_item/4` public



## v3.3.5



- Move logging messages from `info` to `debug` level



## v3.3.4



- Add support for logging via `Logger`.

- Fix some deprecation warnings

- Update github workflow to work again



## v3.3.3



- Fix crash when logging binary values that aren't printable strings, by base64

  encode them.



## v3.3.2



- Revert "Allow `replace` and `replace_all` to work in more situations" as

  it prevented it working in other situations.



## v3.3.1



- Allow `replace` and `replace_all` to work in more situations

- Fix reserved word names in `delete_all`

- Fix removal of empty mapsets when `remove_nil_fields_on_update` is set



## v3.3.0



- Add support for table stream configuration



## v3.2.0



- Fix migrations support for ecto_sql 3.7.2

- Fix warnings on Elixir 1.13

- Raise minimum Elixir version to 1.10

- Add dialyzer run to CI workflow



## v3.1.3



- Support `:empty_mapset_to_nil` for `insert_all` function

- Fix error decoding parameterized field on schema load



## v3.1.2



- Support update operations for the `:empty_map_set_to_nil` option.



## v3.1.1



- Support for `ecto_sql` version 3.6.



## v3.1.0



- Add `:nil_to_empty_mapset` and `:empty_mapset_to_nil` configuration options.



## v3.0.3



- Constrain ecto_sql requirement to 3.5.x. 3.6 introduces interface changes that are not yet supported.



## v3.0.2



- Add handling for `nil` values in `DynamoDBSet.is_equal?`



## v3.0.1



- Maintain backwards compatibility for Ecto versions 3.0 <= 3.4 - all major version 3 releases of Ecto should now be supported



## v3.0.0



### Enhancements



#### Configuration



- Per-repo configuration support



#### Dependencies



- Upgrade to and support for [Ecto](https://github.com/elixir-ecto/ecto) version 3.5 or higher (lower versions not supported by this release)

- Upgrade [ExAws.Dynamo](https://github.com/ex-aws/ex_aws_dynamo) to version 4 - recommend reviewing upgrade guide in that repo

- Upgrade Hackney to v1.17.3