Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>When new model is created and saved with RESTAdapter its Id property is undefined, because my backend is responsible for id generation. </p> </blockquote> <p>Right, but there is nothing unusual about this - ember expects id generation to be done by the backend.</p> <blockquote> <p>So when I return to grid there is 2 same entities: first - with empty Id (from RESTAdapter cache, I think) and second - with correct Id returned from backend.</p> </blockquote> <p>OK. What do you mean by <em>same 2 entities</em> - surely they are different js objects. Try logging each of them to console like this: </p> <pre><code>console.log(entityOne.toString()); console.log(entityTwo.toString()); </code></pre> <blockquote> <p>Any ideas? </p> </blockquote> <p>There are many things that could cause this to happen. Sounds like somehow you are creating two new records and saving just one of them. Or could be the API response does not match what ember expects, causing an extra record to get created.</p> <ul> <li><p>Try to enable logging on your records, then watch console so you can see what's going on as your model is saved. Hopefully this will give you some insight into when/how the extra record is being created. </p> <p>record.set("stateManager.enableLogging", true)</p></li> <li><p>Inspect browser communication with your api and compare JSON to see if it matches what <a href="http://emberjs.com/guides/models/the-rest-adapter/" rel="nofollow">the ember rest adapter</a> expects. </p></li> <li><p>Post that JSON and the rest of your source code (model definition, etc.) to Stack Overflow, maybe a second set of eyes will help.</p></li> <li><p>Check this post for some other debugging tips: <a href="http://www.akshay.cc/blog/2013-02-22-debugging-ember-js-and-ember-data.html" rel="nofollow">http://www.akshay.cc/blog/2013-02-22-debugging-ember-js-and-ember-data.html</a></p></li> </ul> <blockquote> <p>Maybe it is posiible to disable RESTAdapter cache?</p> </blockquote> <p>RESTAdapter does not maintain a separate cache of model objects. And since you are not trying to do anything special, there should be no need to take a step like that. </p>
    singulars
    1. This table or related slice is empty.
    1. POEmber data entity id generation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMike Grassotti
    1. USMike Grassotti
    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. VTBountyClose
    1. COMany thanks for this link, but I still can't fix my issue. I've include some code to my question.
      singulars
      1. PO
      1. USgriZZZly8
    2. COThe code you provided appears to be fine. Updating my answer with some more suggestions on how to track down the issue.
      singulars
      1. PO
      1. USMike Grassotti
    3. COSome new details in my question. I still have no solution. Maybe, it's ember-data bug?
      singulars
      1. PO
      1. USgriZZZly8
 

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