Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Is your reference to the context static, i.e. you've got a single context across the type? That doesn't sound like a great idea to me. Anyway, leaving that to one side, you can do:</p> <pre><code>// Private version which takes a context... private static Func&lt;LINQDBDataContext, string, IQueryable&lt;Pet&gt;&gt; QueryFindByNameImpl = CompiledQuery.Compile(( LINQDBDataContext context, string name) =&gt; from p in context.Pets where p.Name == name select p); // Public version which calls the private one, passing in the known context public static Func&lt;string, IQueryable&lt;Pet&gt;&gt; QueryFindByName = name =&gt; QueryFindByNameImpl(contextFromType, name); </code></pre> <p>EDIT: Okay, if you don't like this approach, you could try writing your own generic wrappers around <code>CompiledQuery.Compile</code> instead. For example:</p> <pre><code>public static class LinqHelpers { public static Func&lt;TArg0, TResult&gt; Compile&lt;TContext, TArg0, TResult&gt; (this TContext context, Expression&lt;Func&lt;TContext, TArg0, TResult&gt;&gt; query) where TContext : DataContext { Func&lt;TContext, TArg0, TResult&gt; compiled = CompiledQuery.Compile(query); return arg =&gt; compiled(context, arg); } } </code></pre> <p>(And so on for more parameters.)</p> <p>I haven't tried even compiling that, but I <em>think</em> it will work. You'd then use it like this:</p> <pre><code>private static MyLinqDataContext context = SomeUtilityClass.GetMeMyContext(); public static Func&lt;string, IQueryable&lt;Pet&gt;&gt; QueryFindByName = context.Compile ((LINQDBDataContext context, string name) =&gt; from p in context.Pets where p.Name == name select p); </code></pre> <p>It's still creating a wrapper of course, but at least you only need to do it in one place. If your objection to creating wrappers was anything other than the tedium/code mess of it, please give more details.</p>
    singulars
    1. This table or related slice is empty.
    1. POLinq compiled queries without passing the context
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJon Skeet
    1. USJon Skeet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCheers, but that's creating a wrapper function which is what I'm trying to avoid.
      singulars
      1. PO
      1. USctrlalt3nd
    2. COThanks. I'm just playing around and thought it might be a useful technique. But it's suprisingly hard to achieve ;)
      singulars
      1. PO
      1. USctrlalt3nd
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload