Databases
StackOverflow2013
Postsdbo
PO$resource query() is not displaying the latest data after a server-side data modification was done
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO$resource query() is not displaying the latest data after a server-side data modification was done
    primarykey
    data
    text
    <p><strong>Scenario</strong></p> <p>The initial $resource query() retrieves an object containing 'A', 'B', &amp; 'C' entries from the server.</p> <p>The user then goes to a different Add Entry Screen and adds a 'D' entry. This Screen is done via a server-side process not via a client-side process.</p> <p>The user now goes back to the first screen and re-queries the $resource query(), however, this is STILL showing the object containing 'A', 'B', &amp; 'C' entries. The 'D' is not in the object retrieved by $resource.</p> <p><strong>Question</strong></p> <p>How can the $resource query() be done so that it can now go to the server and retrieve the latest list?</p> <p><strong>Research</strong></p> <p>The closest I found to an answer is here -> <a href="https://stackoverflow.com/a/17763081/2747683">How to refresh local data fetched using $resource service in AngularJS</a>, however, I'm not sure what the person meant by </p> <blockquote> <p>Adding a new instance to a list in the scope will refresh the list displayed on the page.</p> </blockquote> <p><strong>Some Code Snippets</strong></p> <p>Controller js:</p> <pre><code>angular.module('AutomationApp') .controller('FirstTryController', function ($scope, TestSuites) { $scope.testsuites = {}; TestSuites.query(function (response) { $scope.testsuites = response.TestSuites; }); }); </code></pre> <p>Service js:</p> <pre><code>angular.module('AutomationApp') .factory('TestSuites', function ($resource) { return $resource('/api/listTestSuites/:TestSuiteId', { TestSuiteId: '@TestSuiteId' }, { query: { method: 'GET', params: {}, isArray: false } }); }); </code></pre> <p>app.js:</p> <pre><code>var app = angular.module('AutomationApp', ['ngRoute', 'ngResource']); app.config(function ($routeProvider, $locationProvider) { $routeProvider .when('/list', { templateUrl: 'app/views/firsttry.html', controller: 'FirstTryController', resolve: { delay: function ($q, $timeout) { var delay = $q.defer(); $timeout(delay.resolve, 500); return delay.promise; } } }); }); </code></pre> <p><strong>Recap/Summary</strong></p> <p>On the initial $resource query(), it is retrieving the latest data as expected. However, if the data in the server is modified by some server side process, and the user goes back and reexecutes the $resource query(), the data retrieved does not reflect the newly modified server side data.</p> <p>Thank you in advance.</p> <p>**** ---- EDIT UPDATE ---- ****</p> <p>It appears to be IE 8 related. This code works with Chrome and Mozilla but no with IE 8. Any idea where to go from here? Thank you again.</p> <p><strong>RESOLVED</strong></p> <p>I went with what I found in this post <a href="https://stackoverflow.com/questions/16098430/angular-ie-caching-issue-for-http">Angular IE Caching issue for $http</a>. Thank you Pathsofdesign for supplying the link.</p> <p>I did the following change to make this work (<em>ADDED content inside params {}</em>):</p> <pre><code>Service js: angular.module('AutomationApp') .factory('TestSuites', function ($resource) { return $resource('/api/listTestSuites/:TestSuiteId', { TestSuiteId: '@TestSuiteId' }, { query: { method: 'GET', params: { 'foobar': new Date().getTime() }, isArray: false } }); }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USBuitrago
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    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. COCan you narrow the problem to server-side or client-side? Meaning: this could be caused by the browser caching the data (`query()` is GET I think, so elligible for caching). Can you check the network with Firebug (or equivalent) and verify that the request is actually sent to the server and not retrieved from the cache? Then a breakpoint in the server-side code to see it is actually called, that it actually *does* store D (check with the DB too), and what it fetches from the DB the second time `query()` is called.
      singulars
      1. PO$resource query() is not displaying the latest data after a server-side data modification was done
      1. USNikos Paraskevopoulos
    2. COAppears to definitely be a client-side issue. The DB has the correct information at all times. However, thanks to your comment, I just realized that this is happening with IE only?! At home I use Chrome, but unfortunately, for my job, I have to use IE 8. This same code worked on Chrome and I just installed Mozilla at work (can't install Chrome) and it worked fine with Mozilla as well?! So this definitely seems to be an issue with IE 8. Any idea where to go from here?
      singulars
      1. PO$resource query() is not displaying the latest data after a server-side data modification was done
      1. USBuitrago
    3. COLook at the network tab in chrome, is the server being called on subsequent requests? It could be caching the request and just giving you back the cached results without actually going to the server.
      singulars
      1. PO$resource query() is not displaying the latest data after a server-side data modification was done
      1. USFourth
 

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