王春晖文献翻译.docVIP

（ Retrieving objects Retrieving persistent objects from the database is one of the most interesting (and complex) parts of working with Hibernate. Hibernate provides the following ways to get objects out of the database: Navigating the object graph, starting from an already loaded object, by accessing the associated objects through property access or methods such as aUser.getAddress().getCity(). Hibernate will automatically load (or preload) nodes of the graph while you navigate the graph if the Session is open. Retrieving by identifier, which is the most convenient and perform ant method when the unique identifier value of an object is known. Using the Hibernate Query Language (HQL), which is a full object-oriented query language. Using the, Hibernate Criteria API, which provides a type-safe and object oriented way to perform queries without the need for string manipulation. This facility includes queries based on an example object. Using native SQL queries, where Hibernate takes care of mapping the JDBC result sets to graphs of persistent objects. In your Hibernate applications, you’ll use a combination of these techniques. Each retrieval method may use a different fetching strategy—that is, a strategy that defines what part of the persistent object graph should be retrieved. The goal is to find the best retrieval method and fetching strategy for every use case in your application while at the same time minimizing the number of SQL queries for best performance. We won’t discuss each retrieval method in much detail in this section; instead we’ll focus on the basic fetching strategies and how to tune Hibernate mapping files for best default fetching performance for all methods. Before we look at the fetching strategies, we’ll give an overview of the retrieval methods. (We mention the Hibernate caching system but fully explore it in the next chapter.) Let’s start with the simplest case, retrieval of an object by giving its identifier value (navigating the object gr