-=[ Mr. Bumblebee ]=-
_Indonesia_
ó
î:ïNc @@ s d Z d d l m Z d d l Z d d l j Z d d l m Z m Z d d l m
Z
d e f d „ ƒ YZ d e f d „ ƒ YZ
d
e f d „ ƒ YZ d S( sª This module provides a transactional facility.
Transactions provide hooks to allow data objects (i.e. inventory weaves or
the revision-history file) to be placed in a registry and retrieved later
during the same transaction. Transactions in bzr are not atomic - they
depend on data ordering of writes, so we do not have commit or rollback
facilities at the transaction level.
Read only transactions raise an assert when objects are listed as dirty
against them - preventing unintended writes.
Write transactions preserve dirty objects in the cache, though due to the
write ordering approach we use for consistency 'dirty' is a misleading term.
A dirty object is one we have modified.
Both read and write transactions *may* flush unchanged objects out of
memory, unless they are marked as 'precious' which indicates that
repeated reads cannot be obtained if the object is ejected, or that
the object is an expensive one for obtaining.
i ( t absolute_importN( t IdentityMapt NullIdentityMap( t muttert ReadOnlyTransactionc B@ sY e Z d Z d „ Z d „ Z d „ Z e d „ Z d „ Z d „ Z d „ Z
d „ Z RS( s* A read only unit of work for data objects.c C@ s d S( s Clean up this transaction.N( ( t self( ( s7 /usr/lib/python2.7/dist-packages/bzrlib/transactions.pyt finish3 s c C@ sM t t | ƒ j ƒ t ƒ | _ t ƒ | _ g | _ d | _ t ƒ | _ d S( Niÿÿÿÿ(
t superR t __init__R t mapt sett _clean_objectst _clean_queuet _limitt _precious_objects( R ( ( s7 /usr/lib/python2.7/dist-packages/bzrlib/transactions.pyR 6 s c C@ s
| | j k S( s"