Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your query only asks for the root type, <code>DesignType</code>, so that is all that should be returned. I'll assume that your server side method is not returning the related <code>Product</code> and <code>Vision</code> entities (which it could do but I'm betting that you're not making that happen).</p> <p>So Breeze is doing what you asked.</p> <p>If the client wants the related entities, it can ask for them with an expand clause:</p> <pre><code>breeze.EntityQuery.from("Designs") .expand('Products, Vision') </code></pre> <p>Check out <a href="http://www.breezejs.com/documentation/query-examples#Eager%20loading%20%20EntityQuery.expand" rel="nofollow">the documentation on queries and expand</a></p> <h2>Update 11 Dec 2013</h2> <p>If I understand your comment, (a) you now understand why you don't see <code>Product</code> because you are neither requesting products on the client nor pushing them out from the server, (b) your web api is including the related <code>Vision</code> instance and (b) you are seeing <code>Vision</code> data in the JSON response from the query.</p> <p>The remaining mystery is why <code>someDesignType.Vision</code> is returning null.</p> <p>Please read <a href="http://www.breezejs.com/documentation/query-result-debugging" rel="nofollow">"Query response debugging"</a> focusing in particular on the reference navigation property and the foreign key property on <code>Product</code> that points back to the <code>DesignType</code>. If you're still mystified, please show us how the details of the <code>Vision</code> navigation property as explained there.</p>
    singulars
    1. This table or related slice is empty.
    1. POBreeze metadata and deserializing objects
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWard
    1. USWard
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBreeze metadata and deserializing objects
      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
    1. COMy server side query is : (DbQuery<DesignType>)Context.Include("VisionType"); So at least I was supposed to see the Vision entity. I read this question about (referentialConstraint) , so please your feedback : http://stackoverflow.com/questions/17158159/breeze-returns-navigation-properties-in-the-metadata-but-not-on-the-entities
      singulars
      1. PO
      1. USWasim
    2. COThanks for the update , I updated my question with the two entities , lets ignore product away right now , I think its similar problem. As you can see nothing special , I walked by the book as your documentation . Please let me know if you need any other inputs to figure out the problem.
      singulars
      1. PO
      1. USWasim
    3. COBTW , I read in the Query response debuggin : Did you define foreign key (FK) properties? Developers often neglect to define or identify the FK properties. Breeze requires FK properties to implement navigation properties. In some cases you can define navigation properties without FKs but Breeze will not be able to maintain those properties in cache. How I can do that in EF5 , in the code without doing this in the designer ? Thaks ...
      singulars
      1. PO
      1. USWasim
 

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