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

Expanded support for map type in DynamoDB #339

Merged
merged 2 commits into from
Feb 10, 2015
Merged

Expanded support for map type in DynamoDB #339

merged 2 commits into from
Feb 10, 2015

Commits on Feb 9, 2015

  1. Extend dynamo Attribute to support Map type

    Includes:
    - added TYPE_MAP constant
    - added recursive parsing of map in parseAttributes
    - follow nested structs during output to map[string]interface{}
    - expanded testing of Query/Scan operations so that Map is covered
    - added dummy interface for UpdateExpressionUpdateAttributes and
      failing unit test for it
    tgross committed Feb 9, 2015
    Configuration menu
    Copy the full SHA
    ac0110f View commit details
    Browse the repository at this point in the history

Commits on Feb 10, 2015

  1. Add UpdateExpressionUpdateAttributes to support full UpdateExpression…

    … grammar
    
    The existing UpdateAttributes method on Table could potentially be modified
    to support a limited subset of UpdateExpressions, but it can't currently
    support semantics like "SET #key1=:val1, DELETE #key2=:val2" that are permitted
    by the DynamoDB API.
    
    Providing a method that allows us to pass an UpdateExpression struct will support
    arbitrary UpdateExpressions at the cost of the complexity to actually write one.
    The added complexity only appears when we actually need it, so this seems like a
    good trade off. Examples are provided in the associated test code.
    tgross committed Feb 10, 2015
    Configuration menu
    Copy the full SHA
    eb62881 View commit details
    Browse the repository at this point in the history