Differences between revisions 2 and 3
Revision 2 as of 2007-08-15 16:39:29
Size: 1834
Editor: jp
Revision 3 as of 2008-01-03 13:48:05
Size: 1834
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Transactional variables are data slots which can store arbitrary values during a transaction. Transactional variables are guaranteed to vanish when a transaction finishes or aborts, and specific to a single thread and a single transaction. They are never shared by different threads.

Transactional variables are different from user-defined data in a REQUEST object, in the sense that one request may execute multiple transactions, but not vice versa. If data should persist beyond a transaction, but must not persist over a single request, you should use a REQUEST object instead of transactional variables.

Also, transactional variables are different from volatile attributes, because transactional variables may not disappear within a transaction.

The constraint is that each key must be hashable, so that it can be used as a key to a dictionary.


  from Products.ERP5Type.TransactionalVariable import getTransactionalVariable
  tv = getTransactionalVariable()
    toto = tv['toto']
  except KeyError:
    toto = tv['toto'] = getToto()

Naming Transactional Variable Keys

The following example shows how to name a transactional variable in order to prevent name conflicts:

  acquisition_key = ('_getDefaultAcquiredProperty', self.getPath(), key, base_category,
                      portal_type, copy_value, mask_value, sync_value,
                      accessor_id, depends, storage_id, alt_accessor_id, is_list_type, is_tales_type)

The general form to name transactional variables for ERP5 document methods is:

  key = (<<methodId>>, self.getPath(), arg1, arg2, arg3, etc.)

and if the transactional variable not used on an ERP5 document method:

  key = (<<ModuleId.ModuleId.ClassId.methodId>>, arg1, arg2, arg3, etc.)

HowToUseTransactionalVariable (last edited 2008-01-03 13:48:05 by localhost)