Thomas Witt
Thomas Witt
I totally second this idea of @bmalinconico. The prefix in range keys to differentiate between different types of data is THE access pattern in DynamoDB. Especially also when combined with...
> Regarding the proposed feature with a range prefix. I am not familiar with the concrete patterns of the Single-Table design and don't know whether such range prefixes is a...
@andrykonchin Yes, basically you could already write this with the current version, but I'd say convention over configuration is a very old tried-and-true mantra of Rails. Apart from that, the...
@andrykonchin A full design I would need to think about longer, but how I would approach it if you configure Dynamoid that way (let's say via config.single_table_design = true): -...
Wouldn't it be possible to allow to supply the range key query optionally in the Model of the associated table? My range key is a begins_with selector, so that'd be...
Just FYI, my current workaround is: ``` class Report def destroy_recursive # See https://github.com/Dynamoid/dynamoid/issues/501 c = Company.name(self.company_ids.first) c.company_ids.delete(self.id) c.save self.destroy rescue nil # Avoid the range key error end end...
I would second that, also for Zoom links as well.
Same here. Doesn't run unfortunately on a Raspberry Pi 4
Same problem here like @synthead
@andrykonchin Hey Andrii, just checkin in whether you had time to think about those suggestions …