Unit of Work in ORM

PART 1:

Reference: http://stackoverflow.com/questions/3532258/unit-of-work-pattern-and-history

The concept of Unit Of Work is a central concept of ORMs and has been described by Scott Ambler in his outstanding research on ORM (which dates back to 1998), notably the famous ORM sister papers (now split in several documents):

    -The Design of a Robust Persistence Framework for Relational Databases (older version here)
       --5.1.4 The PersistentTransaction Class <-- this is it
    -The Object-Relational Impedance Mismatch
    -Mapping Objects to Relational Databases: O/R Mapping In Detail
    -Choosing a Primary Key: Natural or Surrogate?

And to my knowledge, most modern ORMs are based on Scott Ambler's papers and share concepts:

    -TopLink has a unit of work, the UnitOfWork.
    -JDO has a unit of work, the PersistenceManager.
    -Hibernate has a unit of work, the Session.
    -JPA has a unit of work, the EntityManager.

So while this concept has emerged as a pattern which has been described by Fowler, Ambler's work clearly predates PoEAA.

Actually, TopLink has been created in the early 90's and thus predates Ambler's work, I just don't know when they introduced their unit of work implementation and if Ambler somehow influenced that or if this is resulting from the convergence of similar ideas.

PART 2:

THINK: relationship between unit of work and transaction, and session/entitymanger as well