Logan Bowers

Is the nature of the problem documented with greater detail anywhere? I'm trying to understand what part of the Live middleware is thread-unsafe.

Got it, that makes sense. So if I’m reading this right, pghoard can’t start on OS X because it attempts to load libc and initialize inotify in a constructor on...

Yup, that seems pretty buggy. I couldn't speak to how easy that is to fix. At the moment, my energy is focused on migrating to the adapter code to the...

So I think the problem here is that on tables with range keys, the 'id' is still only the hash_key. This violates an implied identity: ``` ruby x = MyTable.create...

I edited the title of your bug. The problem is that Chain#limit() (https://github.com/Veraticus/Dynamoid/blob/master/lib/dynamoid/criteria/chain.rb#L115) returns an enumerator of records rather than the chain object itself. It's possibly just a one-line change;...

In this case, "subdomain" is not the is not the hash key for the Website table, so you can't use QUERY (you must always specify the hash key when doing...

It's necessary to use the Client directly instead of the high-level API in order to take advantage of secondary indexes, so I think it's inevitable. I have a branch going...

I'd also love to see a Rails solution for "DISTINCT ON". It's an incredibly powerful construct.

Hi Lisa, That does, indeed sound like a bug. Any chance you can put together a pull request with a fix + the requisite spec?

Hello, Thank you for this improvement! Would you mind making the interface conform to ActiveRecord's API (http://api.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html)? I'd like Dynamoid to conform to ActiveRecord as much as reasonably possible.