Assume I have a class that represents a complex domain object with dozens of properties, such as a pension policy.
The GUI lists all pensions in a summary table that only contains a small subset of those properties.
The application uses an ORM such as .NET's entity framework.
When querying the db to populate the summary table, I don't want to return all details for every policy.
How should I handle this so that loading the summary table only queries the relevent fields? Should I use a seperate object such as PensionSummary? Is there a common approach to this scenario?