Databases
StackOverflow2013
Postsdbo
POExtjs4: How to share data between multiple stores or models?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExtjs4: How to share data between multiple stores or models?
    primarykey
    data
    text
    <p>I'm new to Ext and I'm struggling to figure out Models Stores and Proxies. </p> <p>The server returns one large JSON object. For example.</p> <pre><code>{ "responseHeader":{ "status":0, "QTime":12, "params":{ "facet":"true", "facet.limit":"40" } }, "response":{ "numFound":3806, "start":0, "docs":[ { //Lots of fields "id":"1234", ... //Some array properties "testfield":[ "", "" ], ... } ] }, "facet_counts":{ "facet_queries":{ "email":3806 }, "facet_fields":{ "emailaddress":{ }, "subject":{ "candles":136, "filter":130 }, "fromemail":{ }, //... }, "facet_dates":{ }, "facet_ranges":{} }, "highlighting":{ "some doc id":{ "emailtext":[ " Tel.: blah blah &lt;em&gt;blah&lt;/em&gt;" ], "combined":[ "&lt;em&gt;Email&lt;/em&gt; To: blah blah blah" ] } } } </code></pre> <p>I don't want to load this data more than once, I want to grab data from this object, for example the docs object, and put it into a grid. Then pull out another part to put into a selectbox. </p> <p>How do I load this data once, yet create models and stores to give to grids and selectboxes, from it?</p> <p>From what I read the proxy holds the servers response? So I tried creating a proxy out side of a store. Thinking I could use the same proxy with more than one store.</p> <pre><code>var myProxy1 = Ext.create('Ext.data.proxy.Proxy', { type: 'ajax', url : '../test', reader: { type: 'json', root: 'responseHeader' } }); </code></pre> <p>But when I pass myProxy1 to a store</p> <pre><code>Ext.define('Test', { extend: 'Ext.data.Model', fields: [ {name: 'status', type: 'int'}, {name: 'QTime', type: 'int'}, {name: 'param', type: 'auto'} ] }); var myStore = Ext.create('Ext.data.Store', { model: 'Test', proxy: myProxy1, autoLoad: true, listeners:{ load: function( ths, records, successful, operation, eOpts ){ debugger; } } }); </code></pre> <p>It doesn't work. The load event is never fired. No data is loaded. I can see that the proxy made the request, I see the response from the server, but it doesn't load.</p> <p>If I put the proxy inline it loads.</p> <pre><code>var myStore = Ext.create('Ext.data.Store', { model: 'Test', proxy:{ type: 'ajax', url : '../test', reader: { type: 'json', root: 'responseHeader' } }, autoLoad: true, listeners:{ load:function( ths, records, successful, operation, eOpts ){ debugger; } } }); </code></pre> <p>I was thinking I could have one proxy, attach it to multiple stores, and just change the reader on it before I load the store.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDarin Kolev
    1. USJerinaw
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POExtjs4: How to share data between multiple stores or models?
      1. USsak
      1. VTFavorite
    2. VO
      singulars
      1. POExtjs4: How to share data between multiple stores or models?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POExtjs4: How to share data between multiple stores or models?
      1. USNeverwinterMoon
      1. VTFavorite
    1. This table or related slice is empty.
 

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