Databases
StackOverflow2013
Usersdbo
USkevinml
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USkevinml
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. POPost failing with a nested resource from Ember.js to a Rails API.
      singulars
      1. PTQuestion
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COFinally figured this out. I was able to workaround by not embedding the child objects in the parent, so sending separate POSTs to the API once for the parent, then again for each child which included a parent_id. This was not an ideal solution so I went back to working on an embedded parent/child json request. My original problem was indeed with my Rails API. I followed @dgeb's example again and realized I didn't know much about strong parameters. Thankfully there's a [Railscast](http://railscasts.com/episodes/371-strong-parameters) for that! Once I implemented that correctly I'm good to go!
      singulars
      1. POPost failing with a nested resource from Ember.js to a Rails API.
      1. USkevinml
    2. CO@Pedr - Unfortunately no. It does seem to be an issue with Rails not accepting the JSON I am sending. If I remove the {embedded: 'always'} from the App.store, 2 separate JSON posts are sent for the parent and child with the child having a 'parent_id'. Submitting my POSTs this way are successful, however I would like to just send the 1 post with the embedded parent/child objects. Following this example [https://github.com/dgeb/ember_data_example](https://github.com/dgeb/ember_data_example) and I can't figure out what I am doing different that would cause the error.
      singulars
      1. POPost failing with a nested resource from Ember.js to a Rails API.
      1. USkevinml
    3. COIs it serializing correctly now for the 'date' model?
      singulars
      1. PO
      1. USkevinml
 

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