Join the Persistence Hub before December 10th to become a founding member and get the best price: https://thorben-janssen.com/join-persistence-hub/ DTO projections provide better performance than entities if you only want to read but not change the retrieved information. They avoid the management overhead of an entity class and enable you to only select the database columns your business code needs. But as so often, DTO projections also have a downside, and that’s the handling of associations. When you select an entity object, you can easily traverse all of its managed associations. Doing that with a DTO projection requires a custom result mapping. The JPA specification defines a constructor expression for JPQL queries, which gets executed for each record in the result set and doesn’t support nested constructor calls. That’s more than good enough to map your query result to a flat data structure. But you can’t map a query result that consists of multiple records to a DTO object that contains a list of other complex objects. This video will show you the best way to map such a query result programmatically and how to use Hibernate’s ResultTransformer to let Hibernate handle the result. Like my channel? Subscribe! ➜ http://bit.ly/2cUsid8 Read the accompanying post: https://thorben-janssen.com/fetching-dtos-with-to-many-association/ Links mentioned in the video: https://thorben-janssen.com/dto-projections/ https://thorben-janssen.com/associations/ https://thorben-janssen.com/jpql/ https://thorben-janssen.com/hibernate-resulttransformer/ Want to connect with me? Blog: https://thorben-janssen.com/ Twitter: https://twitter.com/thjanssen123 Facebook: https://www.facebook.com/thorbenjanssenofficial Linkedin: https://www.linkedin.com/in/thorbenjanssen/