aws-sdk-ruby-record

Tag release v2.13.2

References: #141

• Issue - Allow global_secondary_index to be defined in TableConfig without
  supplying capacity settings. (#140)

Tag release v2.13.1

References: #139

• Issue - Do not try to hydrate undeclared attributes from storage on batch_read. (#139)

Tag release v2.13.0

References: #138

• Feature - Allow custom update_expression to be passed through to the
  underlying client calls. (#137)

Tag release v2.12.0

References: #112, #133, #134, #135, #136

• Feature - Allow put, update, and delete item options to be passed through to
  the underlying client calls.

• Feature - Add an original_error accessor to Errors::ConditionalWriteFailed
  which contains the Aws::DynamoDB::Errors::ConditionalCheckFailedException
  error. If :return_values_on_condition_check_failure was provided to a put,
  update, or delete item call, this error will contain the item data that failed
  the condition check.

• Issue - Fix default value for String/Numeric Sets to be unset. (#133)

• Feature - Set required Ruby version to >= 2.3 (#134)

• Issue - Run Rubocop on all files. (#135)

Tag release v2.11.0

References: #129, #132

• Feature - Improve User-Agent tracking and bump minimum DynamoDB version.

Tag release v2.10.1

References: #128

• Issue - Set Aws::Record::VERSION constant from the VERSION file

Tag release v2.10.0

References: #122

• Feature - Implement the BatchGetItem operation (#122)

Tag release v2.9.0

References: #80

• Feature - Add support for inheritance. Aws Record models can now be extended using standard ruby inheritance (#80).

• Feature - Add support for atomic counter (https://github.com/aws/aws-sdk-ruby-record/issues/114)

References #94

• Feature - Add support for on-demand-billing for table migrations (#94)

Tag release v2.5.0

References: #106, #108

• Feature - - Support queries yielding heterogeneous results using (#107)

• Feature - Aws::Record::BuildableSearch - Support queries yielding heterogeneous results using multi_model_filter (#107)

Tag release v2.4.1

References: #100, #104, #72, #95

• Issue - Allow symbols for database_attribute_name
• Issue - Correctly allow lambda/proc for default_value

References: #98

• Feature - Aws::Record::BuildableSearch - Adds support for query and scan builders using substitution expressions. This allows for streamlined and expressive queries and scans using aws-record.

References: #91

• Feature - Aws::Record::Transactions - Adds support for transactional find and transactional get requests. You can learn more about these new APIs in the documentation.

References: #89

• Feature - Aws::Record::TableConfig - Adds support for the "PAY_PER_REQUEST" billing mode in table configurations.

• Issue - Aws::Record::Marshalers::EpochTimeMarshaler - Fixed a bug where epoch time objects didn't properly marshal from database entries.

References: #84

• Feature - Aws::Record::TableConfig - Adds :ttl_attribute to the TableConfig DSL. When used with epoch_time_attr attributes or other attributes stored as epoch time, your TableConfig migrations will enable TTL on your DynamoDB table, and will use your specified attribute as the TTL attribute.

• Feature - Aws::Record::Marshalers::EpochTimeMarshaler - Adds the epoch_time_attr, which behaves much like time_attr except the Amazon DynamoDB storage type is numeric, and the serialized value is epoch seconds.

• Feature - Aws::Record - Add the persisted?, new_record?, and destroyed? methods to Aws::Record, which supports use cases where you'd like to see if a record has just been newly initialized, or has been deleted or was a preexisting record retrieved from DynamoDB. Note that these methods are present in ActiveModel::Model so you should require that module before Aws::Record

• Feature - Aws::Record - Add the assign_attributes, update, and update! methods to Aws::Record which supports the use case where the user might want to mass assign or update a records attributes by hash. update! also ensures that a ValidationError is thrown on an invalid update

• Upgrading - If you already include ActiveModel::Model on your models the new persisted?, new_record? and destroyed? methods will not function properly unless you include ActiveModel::Model before Aws::Record. Additionally, new methods could lead to collisions if you happened to have attributes such as :update or :assign_attributes. In such a case, you would want to version lock below 2.1.0, or use the :database_attribute_name property and change your attribute name in code.

References: #79

• Feature - Aws::Record::Marshalers::TimeMarshaler - Adds the time_attr method to AWS Record models, which uses Time as the underlying type.

References: #75

• Upgrading - Aws::Record - Support version 3 of the AWS SDK for Ruby. This is being released as major version 2 of aws-record, though the APIs remain the same. Do note, however, that we've changed our SDK dependency to only depend on aws-sdk-dynamodb. This means that if you were depending on other service clients transitively via aws-record, you will need to add dependencies on the appropriate service gems when upgrading.