I’m using profile service to store data. I want to clean up the table and make it readable for me by using tables inside tables/nested tables, but I saw a post somewhere and someone said that storing tables inside of tables is less efficient and just to add comments to make it readable. Is that true? If not I will use nested tables.
You will have to add more code to adjust for the structure change, and if any data currently exists you will have to scrap it, which is why some say it is less efficient.
If you think that trade-off is good enough for readability though, go ahead. The performance difference is negligible in the end.
Technically it will be slower since instead of doing a single lookup (tab[“key”]), you’re now doing two (tab[“key”][“key”]). However, computers are fast, and dictionary look ups are relatively fast operations themselves. So basically, the performance difference likely does exist, but it’s so incredibly small that you’re better off going with the more readable option.