wtmoose
commented
9 years ago Being able to track data items across data model versions in order to calculate batch updates is a core feature of the library. So, yes, you’ve got to have a unique ID for each row.
On Jun 26, 2015, at 3:03 PM, Bill Ray notifications@github.com wrote:
Quick and probably stupid question. I have table row values that are duplicates (think of locations for scenes in a movie script...) I need to be able to list them all, i.e., two or more scenes can occur in the same location.
Question: How can I eliminate the above warning (or do I have to fabricate a unique identifier for each row? Can't I just render them in cells, dupes an all)
Brilliant code by the way... Thanx for sharing this
— Reply to this email directly or view it on GitHub https://github.com/wtmoose/TLIndexPathTools/issues/57.
wm-j-ray
Quick and probably stupid question. I have table row values that are duplicates (think of locations for scenes in a movie script...) I need to be able to list them all, i.e., two or more scenes can occur in the same location.
Question: How can I eliminate the above warning (or do I have to fabricate a unique identifier for each row? Can't I just render them in cells, dupes an all)
Brilliant code by the way... Thanx for sharing this