文献翻译-Hibernate in action.docVIP

英文原版 4.1.2 Persistent objects A persistent instance is any instance with a database identity, as defined in chapter 3, section 3.4, “Understanding object identity.” That means a persistent instance has a primary key value set as its database identifier. Persistent instances might be objects instantiated by the application and then made persistent by calling the save() method of the persistence manager (the Hibernate Session, discussed in more detail later in this chapter). Persistent instances are then associated with the persistence manager. They might even be objects that became persistent when a reference was created from another persis- tent object already associated with a persistence manager. Alternatively, a persistent instance might be an instance retrieved from the database by execution of a query, by an identifier lookup, or by navigating the object graph starting from another persistent instance. In other words, persistent instances are always associated with a Session and are transactional. Persistent instances participate in transactions—their state is synchronized with the database at the end of the transaction. When a transaction commits, state held in memory is propagated to the database by the execution of SQL INSERT, UPDATE, and DELETE statements. This procedure might also occur at other times. For example, Hibernate might synchronize with the database before exe- cution of a query. This ensures that queries will be aware of changes made earlier during the transaction. We call a persistent instance new if it has been allocated a primary key value but has not yet been inserted into the database. The new persistent instance will remain “new” until synchronization occurs. Of course, you don’t update the database row of every persistent object in mem- ory at the end of the transaction. ORM software must have a strategy for detecting which persistent objects have been modified by