1Ci Support Help Center home page
Submit a request
Sign in
  1. 1Ci Support
  2. 1C:Enterprise Development Standards
  3. Data processing
  4. Data processing and modification

Using managed lock mode

  • Data processing and modification
    • Transactions: rules of use
    • Using managed lock mode
    • Locking object data for editing from code
    • Responsible data reading
    • Reading specific object attributes from the database
    • Writing events to the user operations history

Scope: managed applications, ordinary applications.

Use a managed lock mode for configurations (set the Data lock management mode property to Managed). Keep in mind the following specifics of this mode:

  • Other transactions cannot read data if incompatible managed locks are set in the current or other transactions.
  • Set explicit managed locks before data is read: 
    • If data being read is subject to further modification. 
    • Data being read must remain unchanged until a transaction is completed.
  • Whenever you set managed locks, make sure you set the lock only to the records, which will be processed by the system as a part of the code processing.
  • We do not recommended that you use the FOR UPDATE clause as it is irrelevant in this mode.

If automatic lock management mode is used, 1C:Enterprise sets a high level of data isolation for transactions on DBMS level. This way application developers make no efforts to exclude non-integral or incorrect data from being received.

However, excessive locks are possible on DBMS level. These locks are caused by lock implementation specifics in DBMS itself. Another reason is that DBMS fails to consider the nature and structure of 1C:Enterprise metadata objects.

See also

  • Using transactions upon reading data
  • General information on excessive locks
  • For more information on switching applications to a managed lock mode, see "Locking data in 1C:Enterprise 8".
© 2020 1C INTERNATIONAL LLC www.1Ci.com Support policy