My previous articles on the Nested GlideRecord issue were far more technical than I usually try to achieve. After all, if I can’t explain it simply enough then I probably don’t understand it well myself. With that in mind, I would like to revisit Nested GlideRecords, how they cause performance problems, and why database indexing alone isn’t the best solution… this time with a little more simplicity. And a parable!