-
Notifications
You must be signed in to change notification settings - Fork 873
Enhancement: Added support for alternate hash and range key datatypes #3
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
Conversation
… (via converters)
|
My specific usecase was the desire to use a Guid for a hashkey... I would be happy to provide sample code if you want to see it in action... Cheers |
|
Can you please post a sample usage of this fix? A class definition, the converter you are using, and usage of the context object with sample data. |
|
Where is a good place for me to post/send a complete working test On Tue, Jul 17, 2012 at 7:10 PM, PavelSafronov <
|
|
Either on GitHub or you can just forward it to me. -----Original Message----- Where is a good place for me to post/send a complete working test case/sample? On Tue, Jul 17, 2012 at 7:10 PM, PavelSafronov < [email protected]
Reply to this email directly or view it on GitHub: |
|
I have a sample application ready for you... What is a good (non-github) email address to send it to? Thanks- -Eric On Wed, Jul 18, 2012 at 10:39 AM, PavelSafronov <
|
|
Thank you for the suggestion, but the problem that this requests attempts to fix is easily resolved using the existing SDK. The suggested code change would allow the markup of a class as follows: Specifically, multiple attributes would be set on a single property. The current version of the SDK does not permit this. However, Guid objects can still be used as Hash and Range keys (though still not as Version), as below: |
|
Learn something new every day... :-) This is a good example of the AWSSDK not being very self documenting Just my opinion... Thanks! Sent from my iPhone On Jul 18, 2012, at 6:23 PM, PavelSafronov
|
|
We're always looking for input like this to improve the SDK, and we'll try to address this specific issue in a future release. |
(via converters)