Skip to content
← Customer Feedback for LINQPad

Settings and activity

2 results found

  1. Autocomplete for SQL

    1,276 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    26 comments  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Hallur Holm Johannessen supported this idea  · 

  2. Allow to set query transaction isolation level

    129 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    13 comments  ·  LINQPad Feature Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Hallur Holm Johannessen commented  · 

    I have been using the following extension method.
    You need to add it to the My Extensions file, which you can see in the My Queries tab.

    public static class MyExtensions
    {
    public static IQueryable<T> DumpNoLock<T>(this IQueryable<T> query)
    {
    using (new System.Transactions.TransactionScope(TransactionScopeOption.RequiresNew,
    new TransactionOptions
    {
    IsolationLevel = System.Transactions.IsolationLevel.ReadUncommitted
    }))
    {
    return query.Dump();
    }
    }
    }

    So now you can dump your query using the following syntax:

    Table1.Where(t1 => t1.Enabled).DumpNoLock()

    Which is equivalent to including the NOLOCK option on your sql query.