Replies: 2 comments
-
|
It's here. Also see this discussion and this gist, and then here's a file of mine using the functions in the gist, SDK v2, UnmarshalMap, Query, etc. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I wonder if AWS team realises that their current implementation is absolutely unusable as is and if after 6 years they will start to consider a decent solution. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a
dynamodbattribute.UnmarshalMapfunction (or similar) for version 2 of the SDK? I'm currently having to use aws-sdk-go instead of aws-sdk-go-v2 for DynamoDB because thedynamodbattribute.UnmarshalMapfunction takes amap[string]*dynamodb.AttributeValueas input, but in SDK v2 the DynamoDB API calls (likeQueryOutputandScanOutput) return a[]map[string]dynamodb.AttributeValue.(I know both return slices, but I'm specifically talking about how aws-sdk-go returns a pointer to AttributeValue, and aws-sdk-go-v2 doesn't).
Beta Was this translation helpful? Give feedback.
All reactions