I have a database which has multiple nested associates. Basically, the structure is as

Question

0

Asked: May 25, 20262026-05-25T02:11:39+00:00 2026-05-25T02:11:39+00:00

I have a database which has multiple nested associates. Basically, the structure is as

0

I have a database which has multiple nested associates. Basically, the structure is as follows:

Order -> OrderItem -> OrderItemPlaylist -> OrderPlaylistItem -> Track -> Artist

I need to generate a report based on all orders sold in a certain date, which needs to traverse into ALL the mentioned associations in order to generate the required information.

Trying to join all tables together would be an overkill, as it would result in an extremely large cartesian join with many redundant data, considering it would be joining 6 tables together. Code below:

q.Left.JoinQueryOver<OrderItem>(order => order.OrderItems)
     .Left.JoinQueryOver<OrderItemPlaylist>(orderItem => orderItem.Playlist)
     .Left.JoinQueryOver<OrderItemPlaylistItem>(orderItemPlaylist => orderItemPlaylist.PlaylistItems)
     .Left.JoinQueryOver<Track>(orderItemPlaylistItem => orderItemPlaylistItem.Track)
     .Left.JoinQueryOver<Artist>(track => track.Artist)

The above works, but with even a few orders, each with a few order items, and a playlist each consisting of multiple tracks, the results would explode to thousand records, growing exponentially with each extra order.

Any idea what would be the best and most efficient approach? I’ve currently tried enabling batch-loading, which greatly scales down the number of database queries but still does not seem to me like a good approach, but more like an ‘easy-workaround’.

There is no need for all the data to be loaded in just one SQL query, given the huge amount of data. One SQL query for each association would be perfect I guess. Ideally it would be something where first you get all orders, then you get all the order items for the order and load them in the associated collections, then the playlists for each order item, so on and so forth.

Also, this doesn’t have to be specifically in QueryOver, as I can access the .RootCriteria and use the Criteria API.

Any help would be greatly appreciated !