Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Let's take them one at a time:</p> <blockquote> <p>Look harder for an existing Linq2SOQL provider (My Google-fu is failing me here, or else there simply isn't one; the only .NET wrapper only mentions Linq as a nice-to-have).</p> </blockquote> <p>Yeah, I doubt one exists already, but hopefully you can find one.</p> <blockquote> <p>Build an expression tree parser. It needs to support, at least, the Select and Where method calls, and needs to either parse lambdas or manipulate their method bodies to get the operations and projections needed. This seems to be a rather massive task, but like I said, it's certainly possible.</p> </blockquote> <p>This is absolutely the way to go if you really are serious about this in the long-run.</p> <blockquote> <p>Wrap the service in Linq2Sql or a similar existing Linq provider that will allow me to extract a close-enough query string, polish it up and pass it to the service. There must be dozens out there (though none that just drop in, AFAIK).</p> </blockquote> <p>What do you mean by "drop in"? You can easily get the SQL straight from L2S.</p> <blockquote> <p>Call Expression.ToString() (or Expression.DebugView), and manipulate that string to create the SOQL query. It'll be brittle, it'll be ugly (behind the scenes), and it will support only what I'm explicitly looking for, but it will provide a rudimentary translation that will allow me to move on.</p> </blockquote> <p>I would strongly discourage you from this approach, as, at minimum, it will be <em>at least</em> as difficult as parsing the expression trees properly. If anything, in order to use this, you'd have to first put the parsed strings into a proper object model -- i.e. the existing expression trees you're starting with.</p> <hr> <p>Really, you should think about building a query provider and doing this right. I think two days is a bit of a stretch though to get something working in even a primitive sense, though it might be possible. IMO, you should research it some at home and toy around with it so you have some familiarity with the basic pieces and parts. Then you might barely be able to get some usable queries going after two days.</p> <p>Honestly though, fully implementing this kind of project is really in the realm of several weeks, if not months -- not days.</p> <p>If that's too much work, you might consider option 3. I'm no expert on SOQL, so no idea what kind of work would be involved transforming ordinary SQL queries into SOQL queries. If you think it's rather algorithmic and reliable, that might be the way to go. </p>
    singulars
    1. This table or related slice is empty.
    1. POLinq to Salesforce "SQL" provider
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKirk Woll
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POLinq to Salesforce "SQL" provider
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBy "drop-in", I mean a Linq provider that isn't pretty tightly coupled to an implementation of the DA layer; Linq2SQL and Linq2Entities, though they do create SQL, are designed to be placed on top of a layer of data access objects which they generate from a schema. I'm not sure I can easily set them up to target the WDSL-generated objects, though if I can, I'm 80% done.
      singulars
      1. PO
      1. USKeithS
 

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