-
Notifications
You must be signed in to change notification settings - Fork 39
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
Need to add rangekey support for Tables #39
Comments
Is this feature actively being worked on? (I'm not sure I have time to work on this at the moment, but wanted to see what the status was in case I had time in the future.) |
Not in the next couple of weeks since we don't need that for our project and it involves some restructuring of the classes. If you find some time feel free to go for it :-) |
I have a pending Pull Request where I added this support. As tnbredillet indicated, it required adding another nesting layer to the Table.items collection via a new ItemRangeGroup class. It also required reworking various AlternatorDBHandler methods to be aware of the extra nesting. If you want to experiment with this revision, you can obtain it from my forked repository branch 'range-key-support': |
Pull request granted, need to revise code. |
Pull request 49 from *thughes" provided "Fix deleting item with range key". I have also discovered that query with a RangeCondition against a table with a numeric Range Key was also failing. I have this fixed in my own forked repository. I will be preparing a branch for submission as a Pull Request sometime this week. |
I submitted my fixes for .query against a table with a numeric Range Key as Pull request 50: |
Currently the Table model doesn't support the RangeKey
The text was updated successfully, but these errors were encountered: