@Woodlandtrek That really isn’t optimal, that’s going to execute an additional query for every user that comes back as part of a collection, or in simple terms: the N+1 problem.
@martinbean yeah, I understand it's not good for large groups. @cml123 shared the context on IRC and was only going to be using it for individual records.
An accessor like that won't be called just because the parent object is returned in a collection, will it? Only if the method is called explicitly?