Databases
StackOverflow2013
Usersdbo
USElte Hupkes
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USElte Hupkes
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    2. PORe-rendering ApplicationView with outlet
      singulars
      1. PTQuestion
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYou mean how to alias the controller? If you check out the routes configuration URL in my answer, there's an example of that if you search the page for "alias". You could map `/admin/users/:action/*` to `array('controller' => 'admin_users', 'plugin' => 'admin')` to get the desired result for the AdminUsersController. If you want to do it automatically for all the controllers in the admin plugin you'd probably have to use a custom route class.
      singulars
      1. PO
      1. USElte Hupkes
    2. CONeither do I at this point, but I'm looking into it ;). What I mean is that Ember.Handlebars.compile() behaves differently than Handlebars.compile(). I originally thought of a solution where I used a custom view inside my translation string (`For some action {{view view.clickHereView}}`), but apparently I cannot access the view helper from there since Ember-I18n uses Handlebars.compile instead of Ember.Handlebars.compile and I can't just replace it. This still seems like the most promising approach though.
      singulars
      1. POTemplate as a variable in Handlebars.js
      1. USElte Hupkes
    3. CO@Jasper That might be possible, however I can already think of a few scenarios in which this isn't sufficient (imagine there being more than one link, the order _might_ not even be accurate). As a workaround I can probably use that (and hope I never run into such an exception case), but I hope there's a better approach.
      singulars
      1. POTemplate as a variable in Handlebars.js
      1. USElte Hupkes
 

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