Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DynamoDB Enhanced Client Versioned Record start at 0 #5565

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Commits on Sep 23, 2024

  1. Refactor DynamoDB Enhanced VersionedRecordExtension internal logic

    The intent is to breakdown the internal logic into smaller methods to make
    the overall flow more obvious to other developers.
    Andy Kiesler authored and akiesler committed Sep 23, 2024
    Configuration menu
    Copy the full SHA
    ecb48de View commit details
    Browse the repository at this point in the history
  2. Add support for starting DynamoDB Record Version with explicit value

    The prior behavior required that a version be initialized with a null value,
    this required mapper clients to use Integer instead of the int primitive.
    This change allows clients to explicitly initialize the version to a value
    which makes it simpler for clients to use primitive values and potentially
    avoid null pointer exceptions and checks.
    
    The default starting value of 0 and increment value of 1 are intended to
    provide sane defaults that are identical to the existing behavior while
    enabling clients to have more fine-graned control over how the versioning
    is managed for their specific use-cases.
    
    The current implementation configures the values at the extension level only
    but the implementation can be expanded to gather the value from the model
    annotation to customize the values on a per table basis.
    Andy Kiesler authored and akiesler committed Sep 23, 2024
    Configuration menu
    Copy the full SHA
    0af21cb View commit details
    Browse the repository at this point in the history