Dynamoid
Dynamoid copied to clipboard
Veraticus
Ruby ORM for Amazon's DynamoDB
Even when setting namespace to nil or leaving it out of my configuration an "_" is prepended to all my table names.
Hey guys, I already saw a ticket about belongs_to assignment auto saving the record, but this seems to happen when any association is assigned. Our dynamoid models double as both...
In my tests, trying to modify a model then reload it to see if the modification method worked, I tried ``` it "updates the event" do controller.book_plan(message) event_reload = Event.find(event.id).reload...
In lib / dynamoid / persistence.rb, line 185, there's a "yield t". There's no check to see if there's a block to yield to. If there's no block passed in,...
DynamoDB supports BETWEEN queries for range keys as noted here: http://docs.aws.amazon.com/AWSRubySDK/latest/AWS/DynamoDB/Client/V20120810.html#query-instance_method Does this mean that support for this in dynamoid won't be available until the adapter is updated to work...
I've got some code as follows, in which DeviceToken is a Dynamoid record and phone_number is its hash_key, but it also has a range key : ``` DeviceToken.where(phone_number: user.phone_number).each do...
ActiveRecord supports "subset conditions", e.g. http://edgeguides.rubyonrails.org/active_record_querying.html has the example: ``` Client.where(orders_count: [1,3,5]) ``` DynamoDB supports "BatchGet" : http://docs.aws.amazon.com/AWSRubySDK/latest/AWS/DynamoDB/BatchGet.html It would seem to be a good matchup. Dynamoid does not currently...
As the [range key paragraph](https://github.com/Veraticus/Dynamoid#range-finding) in the README suggests, I'm searching for past documents: ``` LogEntry.where("created_at.lt" => (DateTime.now - 1.week)).all ``` What I get in return is: ``` AWS::DynamoDB::Errors::ValidationException: One...
In the ManyAssocation module, the method to add an item to an association assumes that the item's id field is called ':id'. Shouldn't it use the key field defined when...
I'm using the console to debug what's going on, and from the stack trace it's clear that as soon as I create a belongs_to association, dynamoid tries to save it...