Differences between get and load methods in hibernate

The fundamental difference between the get method and the load method in Hibernate is that if you use the load method, Hibernate recognizes the object corresponding to this ID (Database record) as existent in the database, so it can be safely used, and it can safely use a proxy to delay loading the object. The database is queried only when other attribute data in the object is used. However, if the record does not exist in the database, no exception can be thrown, the exception thrown by the load method means that when the data of this object is used, the exception is thrown when the data in the database does not exist, rather than when the object is created. Since the session cache is a very cheap resource for hibernate, during load, we will first check the session cache to see if the object corresponding to this ID exists. If it does not exist, we will create a proxy. So if you know that this ID must have a corresponding record in the database, you can use the load method to implement delayed loading.
For the get method, Hibernate checks whether the data corresponding to this ID exists. First, it searches in the session cache and then in the second-level cache. If no data exists, it queries the database, if the database does not exist, null is returned.

For the return types of load and get Methods: although many books have said this: "Get () always returns only entity classes", this is actually incorrect, if the get method finds the object corresponding to this ID in the session cache, if the object is replaced by a proxy, for example, it is used by the load method, or delayed loading by other associated objects, the returned result is the original proxy object instead of the Object Class Object, if the proxy object has not loaded Entity Data (that is, attribute data other than ID), it will query the second-level cache or database to load data, but the returned result is still a proxy object, however, Entity Data has been loaded.

The get method first queries the session cache. If it does not, it queries the second-level cache and the database. Instead, the load method first queries the session cache when it is created. If it does not, a proxy is created, the second-level cache and database are queried only when data is actually used.

In short, there is a fundamental difference between get and load. In a word, Hibernate considers the load method to exist in the database and can safely use the agent to delay loading, if a problem is found during use, only an exception can be thrown. For the get method, Hibernate must obtain the actual data; otherwise, null is returned.