Andrii Konchyn

Could you please provide the exact steps to reproduce the issue? --- Unfortunately, I didn't manage to reproduce the issue on my own. Model declaration: ```ruby class TestTimestamp include Dynamoid::Document...

Ah, I see. It's an expected behaviour. Type casting was introduced in the 3.0 version ([changelog](https://github.com/Dynamoid/dynamoid/blob/master/CHANGELOG.md#300)) and it prevents using raw values in some cases. Type casting for `datetime` field...

The current approach in typecasting is to copy Rails' behavior. As far as I know, Rails doesn't support type casting of Integer value for a DateTime attribute. I don't have...

You can patch type casting of `datetime` attributes in the following way: ```ruby module Dynamoid module TypeCasting module DateTimeTypeCastingWithNumericFormat def process(value) return Time.at(value.to_i) if value.respond_to?(:to_i) super end end DateTimeTypeCaster.send(:prepend, DateTimeTypeCastingWithNumericFormat)...

Hmm, good question. > But, when I use the secondone (with operator in), i'm getting error Not indexed attributes: :user_id.in Looks like it's just a warning, not an error. >...

Yeah, you are right. Dynamoid doesn't support associations for tables with a compound primary key (that's with range key) right now. It isn't mentioned yet in the documentation - my...

It's an interesting idea but right now Dynanoid uses GetItem and BatchGetItem to load associated model/models (to delete them later) and it fails when the required range key is missing.

Could you describe a case when this feature is needed?

I see. Will add this feature request for the next minor release in 3-4 months. So actually there are two options: - to specify config options per model statically -...

Will prioritize this task 👍 .