Databases
StackOverflow2013
Postsdbo
POLinq2Sql - Storing Linq Expressions in cleartext (linq) for future dynamic execution
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POLinq2Sql - Storing Linq Expressions in cleartext (linq) for future dynamic execution
    primarykey
    data
    text
    <p>I recently posted this: </p> <p><A href="https://stackoverflow.com/questions/1558269/linq2sql-storing-complex-linq-queries-for-future-dynamic-execuction-raw-text"><a href="https://stackoverflow.com/questions/1558269/linq2sql-storing-complex-linq-queries-for-future-dynamic-execuction-raw-text">Linq2Sql - Storing Complex Linq Queries for future dynamic execuction - raw text - possible?</a></a></p> <p>It answered one question, but sent me down a different path because of the subQuery needing to reference the same table the original query already exists in.</p> <p>I was able to do exactly what I wanted to do in Linqpad using the "let" keyword.</p> <p>from posMain in DataEventView let posSub = from posSub1 in DataEventView where posSub1.CheckNumber == posMain.CheckNumber &amp;&amp; posSub1.EventTypeID == 7 select posSub1 where posMain.EventTypeID == 6 &amp;&amp; posSub.Any() select posMain</p> <p>That is effectively creating the sub-query I have been attempting to do.</p> <p>Now, I was thinking --- I would really like to dynamically create the IQueryable object in memory, and then my application can have reference to it, and continue to add expressions to it as needed.</p> <p>I am thinking I am going to have to do this with the CodeDom, but there may be a more elegant way of getting the IQueryable from just having Raw Text to start with. Has anyone had to store a linq statement for future execution? These statements are dynamic per customer, so they cant just be complied into the framework. Maybe there is a better idea?</p> <p>Thanks in advance.</p> <p>Travis</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USTravisWhidden
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POLinq2Sql - Storing Linq Expressions in cleartext (linq) for future dynamic execution
      1. USnerraga
      1. VTFavorite
    2. VO
      singulars
      1. POLinq2Sql - Storing Linq Expressions in cleartext (linq) for future dynamic execution
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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