-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Support reading/writing typed structs in DynamoDB #72
Comments
I haven't done a deep comparison between my solution and your goamz one. Barring bugs I am unaware of, mine supports the same semantics as encoding/json -- eg nested types, pointer fields, etc. I do not support int or string sets yet mapping into attribute values. How does that compare to what you have implemented so far? |
My version doesn't support sets either as the intention was to map to and from structs representing JSON documents, and there is no built in representation of sets. It supports all the JSON struct tags since it leverages Overall the implementations look fairly similar to me. |
+1 on this add. currently using the marshaling on goamz |
@cbroglie given my comment in AdRoll/goamz#308 (comment), I'd be happy to help out on this ticket here in any way I can. |
This is just an initial implementation, and it doesn't include support for advanced functionality like conditional operations. As such, the API will likely need to change. But it's a first step towards simplifying reading/writing typed objects from DynamoDB (see aws#72)
Closing since #231 was merged |
Instead of making callers deal with items of the form
map[string]dynamodb.AttributeValue
, it's convenient to be able to read and write typed structs.I previously implemented a solution for goamz (AdRoll/goamz#276), and the same approach will work as both projects use similar types (compare https://github.com/awslabs/aws-sdk-go/blob/master/gen/dynamodb/dynamodb.go#L334 to https://github.com/AdRoll/goamz/blob/master/dynamodb/dynamizer/dynamizer.go#L18).
Happy to look into porting over my changes if there is interest in a similar solution.
The text was updated successfully, but these errors were encountered: