Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMmY2Y2U5NDI0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16645?atlOrigin=eyJpIjoiMmY2Y2... ) HHH-16645 ( https://hibernate.atlassian.net/browse/HHH-16645?atlOrigin=eyJpIjoiMmY2Y2... ) XxxxLoadAccess and EntityGraphs ( https://hibernate.atlassian.net/browse/HHH-16645?atlOrigin=eyJpIjoiMmY2Y2... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 19/May/2023 08:54 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Currently, on some of the LoadAccess APIs, you can do: * .with(graph) with graph interpreted as a “load” graph, and * .with(graph, GraphSemantic.FETCH) to be explicit. There’s no very good reason to prefer LOAD as the default here, and indeed, I think it’s very nonobvious. Also, typing.with(graph, GraphSemantic.FETCH) annoying. So I propose: * deprecate the first one, and * add {{fetching(graph)}}and {{loading(graph)}}which are more explicit, easier to type, and more fluent. ( https://hibernate.atlassian.net/browse/HHH-16645#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16645#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- sha1:9dd72a2 )