[FEATURE] Add NULL DynamoDB Attribute Type
See original GitHub issueSummary:
Dynamoose should support the DynamoDB NULL Attribute Type.
Other information (if applicable):
When we implement this we need to add the following test to Document.isDynamoObject
:
{
"input": {"id": {"S": "foo" }, "data": {"NULL": true}},
"output": true
}
Related Issues:
Other:
- I have read through the Dynamoose documentation before posting this issue
- I have searched through the GitHub issues (including closed issues) and pull requests to ensure this feature has not already been suggested before
- I have filled out all fields above
- I am running the latest version of Dynamoose
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Amazon DynamoDB now supports empty values for non-key ...
Amazon DynamoDB now supports empty values for non-key String and Binary attributes in DynamoDB tables. Empty value support gives you greater ...
Read more >Dynamo DB + In put Item Request how to pass null value?
You can use AttributeValue null type as a placeholder. If you cannot change the type, then, choose ...
Read more >How does DynamoDB handle NULL, empty and undefined fields
When writing an item to DynamoDB, omit nullable string fields altogether (or set them to undefined in the JS SDK) instead of setting...
Read more >Working With DynamoDB Columns/Attributes [incl. Examples]
In order to add attributes, you need to first create a table. You can use AWS Console, AWS CLI, AWS SDK, or the...
Read more >Amazon DynamoDB: What It Is and 10 Things You Should Know
5. Amazon DynamoDB's Data Model · Hash Type Primary Key: If an attribute uniquely identifies an item, it can be considered as Primary....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Could I please get some people to review and test #1061? I believe this should fix everyones issues. Remember to use the new
dynamoose.NULL
property type.I had the same problem. I was able to safely save the document but couldn’t get it. I got the error “TypeMismatch: Expected key to be of type boolean, instead found type object.” Unfortunately it happened in production and I can’t wait for an improvement in Dynamoose. I solved it with the AWS SDK DynamoDB client.
I think Dynamoose is a great library that delivers a better developer experience than the AWS SDK, but this issue forced me to migrate to the AWS SDK.