-
Notifications
You must be signed in to change notification settings - Fork 863
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 DateOnly / TimeOnly in DynamoDBContext #3673
Comments
I'm willing to implement this functionality if it is approved. |
Refer How to use the DateOnly and TimeOnly structures. Needs review with the team. |
I'm thinking the changes would be localized to the converters and some list containing the list of converters. So as long as the change is for the most part contained in that area and we don't have to add a lot of I assume the actual format being saved in DDB for these time data types should be the same we use |
Yeah, it should affect DynamoDBEntryConversion (SetVxConvertions), SchemaV1, SchemaV2.
DynamoDB uses
|
That works for me. Thanks for confirming the DateTime parse with the shorten formatting for these types will work in the fallback parse. |
Describe the feature
I would be nice if DynamoDBContext supported DateOnly / TimeOnly properties natively.
Currently users have to implement custom converters to allow that.
Use Case
Storing data which has only date information, without time.
Proposed Solution
Add
(Behavior is identical for both versions).
DateOnly / TimeOnly types are not available in netstandard, so this functionality should only be available for supported target frameworks.
Other Information
No response
Acknowledgements
AWS .NET SDK and/or Package version used
AWSSDK.DynamoDBv2 3.7.405.28
Targeted .NET Platform
.NET 8
Operating System and version
AmazonLinux
The text was updated successfully, but these errors were encountered: