Subject | Re: How to implement SQLServer's WITH(NOLOCK) statment? |
---|---|
Author | real_yoni |
Post date | 2008-04-14T12:32:09Z |
I need a clarification... NOLOCK enables the SELECT statments to read
uncommitted data. That is: if another process runs an UPDATE statment
the SELECT statment will not get locked.
This is what SQL Server calls a hint which override the default
behaviour (read committed and get locked)
Does firebird support this? If not can I make sure that the default
behaviour would be "read uncommited"?
Thanks,
Yoni.
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:
uncommitted data. That is: if another process runs an UPDATE statment
the SELECT statment will not get locked.
This is what SQL Server calls a hint which override the default
behaviour (read committed and get locked)
Does firebird support this? If not can I make sure that the default
behaviour would be "read uncommited"?
Thanks,
Yoni.
--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:
>a
> real_yoni wrote:
> > Hi,
> >
> > In SQLServer I can force a select statment to ignore any locks on
> > table (in effect having a shared read on the table).
> > SELECT * FROM Items WITH(NOLOCK).
> >
>
> As long as you're doing a select (not an insert/update/delete) locks
> and your transaction isolation mode is concurrency (aka repeatable
> read) or read committed, locks will not apply.
>
>
> Regards,
>
>
> Ann
>