Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The reason that you aren't seeing a request fired off is that as part of the $http call, the config is passed around to each interceptor as a promise.</p> <p><a href="https://github.com/angular/angular.js/blob/b99d064b6ddbcc9f59ea45004279833e9ea82928/src/ng/http.js#L665-L670" rel="nofollow">https://github.com/angular/angular.js/blob/b99d064b6ddbcc9f59ea45004279833e9ea82928/src/ng/http.js#L665-L670</a></p> <p>In angular, $q promises are only resolved at the beginning of a $digest cycle. As a result, your HTTP request won't even be fired off until a $digest cycle happens, which is why you're seeing that wrapping a $timeout around it helps ( a timeout causes a $digest ).</p> <p><a href="https://github.com/angular/angular.js/blob/2a5c3555829da51f55abd810a828c73b420316d3/src/ng/q.js#L160" rel="nofollow">https://github.com/angular/angular.js/blob/2a5c3555829da51f55abd810a828c73b420316d3/src/ng/q.js#L160</a> <a href="https://github.com/angular/angular.js/blob/3967f5f7d6c8aa7b41a5352b12f457e2fbaa251a/src/ng/rootScope.js#L503-L516" rel="nofollow">https://github.com/angular/angular.js/blob/3967f5f7d6c8aa7b41a5352b12f457e2fbaa251a/src/ng/rootScope.js#L503-L516</a></p> <p>You can also verify this by re-creating the error condition you're seeing and watching network requests. After you run this, you should see your request fire off:</p> <pre><code>angular.element( "[ng-app]" ).scope().$digest() </code></pre> <p>That code fires off a $digest cycle on the $rootScope, causing your unresolved promises to become resolved.</p> <p>See this issue for more discussion, because I agree that this is surprising behavior.</p> <p><a href="https://github.com/angular/angular.js/issues/2881" rel="nofollow">https://github.com/angular/angular.js/issues/2881</a></p>
    singulars
    1. This table or related slice is empty.
    1. POAngular resource call not fired when called from $scope.$watch
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdherman
    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 your answer, I suspected this kind of issue. Do you have an idea why it works in this fiddle http://jsfiddle.net/jefmathiot/xCJjc/4/ ? I tried to be really close to our real use case (a click in a directive that changes a property in of the nested directive which fires an Ajax call) but I can't understand why in this particular case the $digest cycle is executed.
      singulars
      1. PO
      1. USJef
    2. COI'm in the realm of guessing without seeing your exact source, but if you look at the link I posted to the rootScope source, you can see that the asyncQueue is being processed as a part of the do/while loop in the $digest. That actually means that if your scope isn't the last scope that processed, you may see that it works as expected. If it IS the last scope that's processed, the asyncQueue won't be drained until the next $digest
      singulars
      1. PO
      1. USdherman
    3. COIt seems that you guess pretty well :), but I'm a bit lost. In the rootScope source code, the do-while loop seems to be processed as long as there are elements into the asyncQueue. Calling a resource isn't supposed to append an element into this queue ?
      singulars
      1. PO
      1. USJef
 

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