In article <2qlvrr$jin@delphinium.cig.mot.com>,
Dave Tomlinson <tomlnsn@rtsg.mot.com> wrote:
& In article <2qdouo$513@david.wheaton.edu>, gmribeir@david.wheaton.edu (Glauber Ribeiro) writes:
& |> Browsing through some come that i maintain, i found a command
& |>
& |> SET ISOLATION TO DIRTY READ
& |>
& |> I couldn't find this in the documentation i have. The command
& |> apparently works both from 4GL and ESQLC.
& |>
& |> Can anybody tell me what this is supposed to do?
& |> Also, are there other options or variations for this command?
& |>
& |> Thank you very much for any help.
& |>
&
& SET ISOLATION TO DIRTY READ will fetch data whether or not it has been
& committed and will neither place nor respect locks.
Mening that it will even read a row that has been locked in
exclusive mode? (Note, not a table locked in exclusive mode, just
one or more rows locked in exclusive mode.)
Thanks again,
Glauber
--
glauber ribeiro
glauber@david.wheaton.edu
-------------------------
ja nehovorim po slovensky