Here is a table i built for managing storage, the values in column "current_quantity" change along the model running. Then i'm wondering is Table.addIndex() preferable in this situation?(eg. add index for column "part_no")
As you quoted from manual, it is not intended for this kind of use. If you do it on another more static case like slots, then you could benefit from an index.
Also - consider using a list with fields instead - then you can more easily listen to events and select quantities that match requirements.
Another more static value would be SKU values. If you look up for a value like a SKU and another field contains available amount of items and their location as string or pointer in arrays, an index can speed up your search. Important would be to keep even SKU values in your table, if there aren’t any items associated with. If your SKU pattern involves already directly a table row number you need not anymore an index.
15 People are following this question.
