ExtJS的4.1 - 选举中Model.Save相关数据（）响应 [英] ExtJS 4.1 - Returning Associated Data in Model.Save() Response
问题描述
我很好奇，为什么包含在结果集的记录的 Model.save（）响应不正确，返回更新相关的数据，尽管更新后的数据被包含在服务器响应...
I am curious as to why the record contained in the result set of a Model.save() response does not properly return updated associated data, despite the updated data being contained in the server response...
示例模式和放大器;商店定义：
Ext.define("App.model.test.Parent",{
extend: 'Ext.data.Model',
requires: ['App.model.test.Child'],
fields: [
{name: 'id', type: 'int' },
{name: 'name', type: 'string'},
{name: 'kids', type: 'auto', defaultValue: []}
],
idProperty: 'id',
hasMany: [{
foreignKey: 'parent_id',
model: 'App.model.test.Child',
associationKey: 'kids',
name: 'getKids'
}],
proxy: {
type: 'ajax',
api : {
create: '/service/test/create/format/json',
read : '/service/test/read/format/json',
update : '/service/test/update/format/json'
},
reader: {
idProperty : 'id',
type : 'json',
root : 'data',
successProperty : 'success',
messageProperty : 'message'
},
writer: {
type : 'json',
writeAllFields : true
}
}
});
Ext.define("App.model.test.Child",{
extend: 'Ext.data.Model',
fields: [
{name: 'id', type: 'int' },
{name: 'name', type: 'string'},
{name: 'parent_id', type: 'int'}
]
});
Ext.define("App.store.test.Simpson",{
storeId: 'TheSimpsons',
extend: 'Ext.data.Store',
model : 'App.model.test.Parent',
autoLoad: true,
autoSync: false
});
应用程序服务器响应代理的读与单个模型的要求，及其相关数据。这是所有工作虎背熊腰，脚蹬dory没问题！
The application server response to the proxy's READ request with a single model, and its associated data. This is all working hunky dory!
服务器响应读取请求
{
"data":{
"id":1,
"name":"Homer Simpson",
"children":{
"1":{
"id":1,
"name":"Bart Simpson"
},
"2":{
"id":2,
"name":"Lisa Simpson"
},
"3":{
"id":3,
"name":"Maggie Simpson"
}
}
},
"success":true,
"message":null
}
的到目前为止，一切都在按计划工作... 的
store = Ext.create("App.store.test.Simpson");
homer = store.getById(1);
kids = homer.getKids().getRange();
console.log("The Simpson Kids", kids); // [>constructor, >constructor, >constructor]
不需要的行为用保存的开始和更新请求
下面是我在更新测试响应请求...
Here is my test response for the UPDATE Request...
/** Server UPDATE Response */
{
"data":{
"id":1,
"name":"SAVED Homer Simpson",
"kids":[{
"id":1,
"name":"SAVED Bart Simpson",
"parent_id":1
},{
"id":2,
"name":"SAVED Lisa Simpson",
"parent_id":1
},{
"id":3,
"name":"SAVED Maggie Simpson",
"parent_id":1
}]
},
"success":true,
"message":null
}
/** Will call proxy UPDATE, response is above */
homer.save({
success: function(rec, op){
var savedRec = op.getRecords().pop(),
kidNames = '';
console.log(savedRec.get('name')); // SAVED Homer Simpson = CORRECT!
Ext.each(savedRec.getKids().getRange(), function(kid){
kidNames += kid.get('name') + ", ";
});
console.log(kids);
//Outputs: Bart Simpson, Lisa Simpson, Maggie Simpson = WRONG!!
}
})
我发现，如果我检查由服务器生成的公会商店返回的记录（即 getKidsStore ）包含的记录是原始记录，也就是说，他们这样做没有拯救在他们的名字。在孩子返回的记录的属性，但是，确实包含正确的数据。
I notice that if I inspect the record returned by the server, the generated Association Store (i.e., getKidsStore) the contained records are the original records, i.e., they do not have "SAVED" in their name. The kids property of the returned record, however, DOES indeed contain the correct data.
如果我理解正确的问题，那就是 Ext.data.reader.Reader 不正确地包含在<$相关的数据更新相关商店C $ C> .save（）响应。如果是这样，在我看来，这是很直观，我会期望相同的行为作为处理 store.load（）请求，并填充产生联想专卖店读者开始的时候。
If I understand the issue correctly, it is that the Ext.data.reader.Reader does not correctly update the associated store with the associated data contained in the .save() response. If so, in my opinion, this is very unintuitive as I would expect the same behavior as the reader that handles the store.load() request and populates the generated association stores to begin with.
任何人都可以点我在正确的方向在实现我追求的行为？
Can anyone point me in the right direction in achieving the behavior I'm after?
声明：同样的问题在这里问：的 ExtJS的4 - 负载嵌套的记录数据保存，但没有回应。我觉得我的问题是更彻底一点..
Disclaimer: Same question was asked here: ExtJs 4 - Load nested data on record save but with no response. I feel my question to be a bit more thorough..
编辑：我已经贴过这个问题上煎茶论坛：的http://www.sencha.com/forum/showthread.php?270336-Associated-Data-in-Model.save()-Response
I have posted this question over on the Sencha forums: http://www.sencha.com/forum/showthread.php?270336-Associated-Data-in-Model.save()-Response
修改（13年8月23日）：我重新写这个帖子有一个完整的例子，以及其他的调查结果...
EDIT (8/23/13): I re-wrote this post with a COMPLETE example, as well as additional findings...
推荐答案
我已经找到了问题，或者说，的困惑的在于 getRecords（）的 Ext.data.Operation 的方法。此方法返回的运行的初始配置的记录将被退回，虽然代理可以在某些点上操作被初始化后修改这些记录的数据。的按文档。
I've found the issue, or rather, confusion lies in the getRecords() method of the Ext.data.Operation. This method returns "the operation's initially configured records will be returned, although the proxy may modify these records' data at some point after the operation is initialized." as per the documentation.
这是相当混乱IMO，作为返回的记录确实更新，但是所产生的联想专卖店，因此相关的数据，是不是！这是导致我的混乱，就出现好像该记录包含从应用服务器的更新的数据，但是这并非如此。
This is rather confusing IMO, as the returned record is indeed updated, however the generated association store, and therefore associated data, is not! This is what lead to my confusion, it appeared as though the record contained the updated data from the application server, but this was not the case.
为了帮助我的脑海简单在获得的全更新数据的反应，我添加了一个到方法 Ext.data.Operation 类...我只是写了这个方法，并没有测试需要您自担风险它比确保我一直在寻找的功能，因此使用！
In order to aid my simple mind in obtaining the FULLY updated data from the response, I have added a method to the Ext.data.Operation class... I just wrote this method and haven't tested it more than ensuring the functionality I was looking for, so use at your own risk!
请记住，我不叫store.sync（），而我实例化一个模型，并调用model.save（）方法，所以我的resultSet通常只包含单个记录...
Please keep in mind that I do not call store.sync(), rather I instantiate a model and call the model.save() method, so my resultSet typically only ever contains a single record...
Ext.override(Ext.data.Operation,{
getSavedRecord: function(){
var me = this, // operation
resultSet = me.getResultSet();
if(resultSet.records){
return resultSet.records[0];
}else{
throw "[Ext.data.Operation] EXCEPTION: resultSet contains no records!";
}
}
});
现在我能实现我的功能后...
Now I am able to achieve the functionality I was after...
// Get the unsaved data
store = Ext.create('App.store.test.Simpson');
homer = store.getById(1);
unsavedChildren = '';
Ext.each(homer.getKids().getRange(), function(kid){
unsavedChildren += kid.get('name') + ",";
});
console.log(unsavedChildren); // Bart Simpson, Lisa Simpson, Maggie Simpson
// Invokes the UPDATE Method on the proxy
// See original post for server response
home.save({
success: function(rec, op){
var savedRecord = op.getSavedRecord(), // the magic! /sarcasm
savedKids = '';
Ext.each(savedRecord.getKids().getRange(), function(kid){
savedKids += kid.get('name') + ',';
});
console.log("Saved Children", savedKids);
/** Output is now Correct!!
SAVED Bart Simpson, SAVED Lisa Simpson, SAVED Maggie Simpson
*/
}
});
编辑13年12月10日
我还添加了一个方法来 Ext.data.Model 我称之为 updateTo 它处理更新记录所提供的记录，也可以用来处理关联。我结合使用上述 getSavedRecord 方法。请注意，这不处理，因为我不，我的应用程序使用它们，但这些功能很容易添加任何的belongsTo 的关联。
Edit 12/10/13
I also added a method to Ext.data.Model which I called updateTo which handles updating a record to the provided record, which also handles associations. I use this in conjunction with the above getSavedRecord method. Please note this does not handle any belongsTo associations as I don't use them in my application, but that functionality would be easy to add.
/**
* Provides a means to update to the provided model, including any associated data
* @param {Ext.data.Model} model The model instance to update to. Must have the same modelName as the current model
* @return {Ext.data.Model} The updated model
*/
updateTo: function(model){
var me = this,
that = model,
associations = me.associations.getRange();
if(me.modelName !== that.modelName)
throw TypeError("updateTo requires a model of the same type as the current instance ("+ me.modelName +"). " + that.modelName + " provided.");
// First just update the model fields and values
me.set(that.getData());
// Now update associations
Ext.each(associations, function(assoc){
switch(assoc.type){
/**
* hasOne associations exist on the current model (me) as an instance of the associated model.
* This instance, and therefore the association, can be updated by retrieving the instance and
* invoking the "set" method, feeding it the updated data from the provided model.
*/
case "hasOne":
var instanceName = assoc.instanceName,
currentInstance = me[instanceName],
updatedInstance = that[instanceName];
// Update the current model's hasOne instance with data from the provided model
currentInstance.set(updatedInstance.getData());
break;
/**
* hasMany associations operate from a store, so we need to retrieve the updated association
* data from the provided model (that) and feed it into the current model's (me) assocStore
*/
case "hasMany":
var assocStore = me[assoc.storeName],
getter = assoc.name,
newData = that[getter]().getRange();
// Update the current model's hasMany association store with data from the provided model's hasMany store
assocStore.loadData(newData);
break;
// If for some reason a bogus association type comes through, throw a type error
// At this time I have no belongsTo associations in my application, so this TypeError
// may one day appear if I decide to implement them.
default:
throw TypeError("updateTo does not know how to handle association type: " + assoc.type);
break;
}
});
// Commit these changes
me.commit();
return me;
}
所以基本上我做这样的事情（这在理论上是订单控制器）
So basically I do something like this (this would theoretically be in the Order controller)
doSaveOrder: function(order){
var me = this, // order controller
orderStore = me.getOrderStore(); // magic method
// Save request
order.save({
scope: me,
success: function(responseRecord, operation){
// note: responseRecord does not have updated associations, as per post
var serverRecord = operation.getSavedRecord(),
storeRecord = orderStore.getById(order.getId());
switch(operation.action){
case 'create':
// Add the new record to the client store
orderStore.add(serverRecord);
break;
case 'update':
// Update existing record, AND associations, included in server response
storeRecord.updateTo(serverRecord);
break;
}
}
});
}
我希望这可以帮助别人，因为我是谁被搞糊涂了！
I hope this helps someone who was confused as I was!
这篇关于ExtJS的4.1 - 选举中Model.Save相关数据（）响应的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
