Transaction Isolation Level

Hi,

I have 1 SQL statement selecting data from various tables and updating other
tables.

The question then is how do I prevent other applications from modifying the
tables that I'm working on (that is while my transaction is being executed)?


I know that the isolation level should be either REPEATABLE READ or
SERIALIZABLE. But I need confirmation on if one of these actually solve my
issue - prevents other applications/threads from modifying/inserting data
into the same tables that I'm working on.



Thanks in advance,
Daniel


.

Relevant Pages

  • Re: [PATCH] - support inheritance of mlocks across fork/exec V2
    ... Together with patches to keep mlocked pages off the LRU, ... prefaulting and residency for applications that don't mlock themselves. ... processes is the root of many nasty surprises, ... mempolicy without modifying the source. ...
    (Linux-Kernel)
  • Re: want help with connection codes pls.
    ... DB2 etc. sample codes on how to work on those ... > databases through the applications like accessing and modifying ...
    (comp.programming)
  • Re: Select Case Me.Form?
    ... I specialize in adding more functionality to existing applications, ... modifying existing applications and fixing problems in existing ...
    (microsoft.public.access.formscoding)