JD
> Hi all, > > > > I started last week to use this library hoping it is mature enough. I am facing the same issue with `v0.3.5`, and looks...
> If I use the default function, the index is not updated when start_at is changed. It should if you set `onUpdate` to true.
> when I didn't update the startAt attribute, it sets my index to undefined. That makes sense. How else would it know what to set the value to?
> It would be nice to be able to somehow not update the index. Then don't use `onUpdate` and set the value manually when you need to. You need to...
You should seperate your key and your data (business) attributes. Key attributes are used for accessing an item. Data / business attributes are used to rehydrate your business entities. Therefore,...
P.s. you should use default functionality rather than the prefix functionality as that will be deprecated _soon_.
> Is the best practice you mention to not store data in the key only true for partition keys but not sort keys? Best practice is to seperate all keys...
You are right - there is no pre-canned way to do this. It depends very much on how you designed your entities as to how you would perform this update....
No. I'm not sure how this would work... you have to design your own table and this is _very_ unique to each use case. Nothing stopping you from writing your...
Can you give a full end to end example? This is working in my code (I use it a lot for calculating indices).