Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here's an example of the code I've used in the application I'm working on, not sure it will help much because its not much different than how you have it already.</p> <p><strong>Routing</strong></p> <pre><code>.when('/view/proposal/:id',{ controller : 'viewProposalCtrl', templateURL : 'tmpls/get/proposal/view', resolve : viewProposalCtrl.resolveViewProposal }) </code></pre> <p><strong>Controller</strong></p> <pre><code>var viewProposalCtrl = angular.module('proposal.controllers') .controller('viewProposalCtrl',['$scope','contacts','details','rationale', function($scope,contacts,details,rationale){ $scope.contacts = contacts; $scope.details = details; $scope.rationale = rationale; // [ REST OF CONTROLLER CODE ] }); // proposalSrv is a factory service viewProposalCtrl.resolveViewProposal = { contacts : ['$route','proposalSrv',function($route,proposalSrv){ return proposalSrv.get('Contacts',$route.current.params.id) .then(function(data){ return data.data.contacts; },function(){ return []; }); }], details : ['$route','proposalSrv',function($route,proposalSrv){ return proposalSrv.get('Details',$route.current.params.id) .then(function(data){ return data.data.details; },function(){ return {}; }); }], rationale : ['$route','proposalSrv',function($route,proposalSrv){ return proposalSrv.get('Rationale',$route.current.params.id) .then(function(data){ return data.data.rationale; },function(){ return {}; ] }] }; </code></pre> <p>Now that I think about it, when I was developing my application I did have a problem and not sure why when I named my resolve function "resolve." This gave me a problem:</p> <pre><code>.when('/path',{ // stuff here resolve : myCtrlr.resolve }) </code></pre> <p>but this did not:</p> <pre><code>.when('/path',{ //stuff here resolve : myCtrlr.myResolveFn }) </code></pre> <p><strong>Another Possibility</strong></p> <p>The only other thing I can think of, is that you're returning the <strong>promise</strong> from the <code>$http</code> call and then trying to use <code>appData.data</code> Try using the <code>.then</code> function or one of the other functions (<code>.success</code>,<code>.error</code>) to retrieve the information from the promise.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing resolve in $routeProvider causes 'Unknown provider ...'
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USm.e.conroy
    1. USm.e.conroy
    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
    1. COThanks for this example. My problem is that I cannot even inject the functions to actually use the then() or .success,.error) . I still cannot figure out why. I am beginning to think that angularjs 1.2.5 is doing something differently than before..
      singulars
      1. PO
      1. USGeorgi Angelov
    2. COThat's a possibility, a lot has changed since 1.1.5. Perhaps you're missing a module or something, maybe something was factored out of the core code much like `ngRoute`
      singulars
      1. PO
      1. USm.e.conroy
    3. COI just posted the solution to this problem.
      singulars
      1. PO
      1. USGeorgi Angelov
 

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