Mike Conner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=62fe3d3... ) *commented* on HHH-15628 ( https://hibernate.atlassian.net/browse/HHH-15628?atlOrigin=eyJpIjoiOGY5MT... ) Re: OneToOne relationship is null when hibernate.max_fetch_depth = 1 ( https://hibernate.atlassian.net/browse/HHH-15628?atlOrigin=eyJpIjoiOGY5MT... ) So, I just realized that this may be a result of the order in which I created my test data. I first created a Device, persisted that, then created a DevClientId, set the Device on the DevClientId, but not the other way around. For whatever reason, this sometimes works if max_fetch_depth is set to 2, but since both sides of the relationship are not properly set when persisted, I’m assuming the testcase is not valid. I’ve still got a problem related to a similar mapping, dealing with data loaded from a database (oracle), but I don’t believe the test case replicates that problem. ( https://hibernate.atlassian.net/browse/HHH-15628#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15628#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#100209- sha1:6031644 )