属性更改未通知，表未更新

Question

我想更新表，但更新SQL未执行，因此更改无效。

详情：

最初issue.name我们'问题'。我想改成'qqqqqqqqqqqq'。

控制器：

def update 
if params['cancel'] 
    redirect_to(@issue) 
    return 
end 
@issue = Issue.find(params[:id]) 
logger.debug "original object" 
logger.debug "#{@issue.to_yaml}" 
logger.debug 'bulk attribute settings...' 
@issue.attributes= params[:issue] 
logger.debug "after bulk settings" 
logger.debug "#{@issue.to_yaml}" 

@issue.events.build(:note=>params[:issue][:description],:verb=>'Edited', :changes=>@issue.textalize_changes) 

if @issue.save 
    logger.debug "after save" 
    logger.debug "#{@issue.to_yaml}" 
    redirect_to(@issue) 
else 
    render :action => "edit" 
end 
end 

一个额外的代码fregment可能是有趣的是textalize_changes：

def textalize_changes 
r = "" 
if changed? 
    changes.keys.each do |k| 
    r << "#{k.humanize} changed " 
    r << "from `#{translate(k,changes[k][0])}` " 
    r << "to `#{translate(k,changes[k][1])}`" 
    r << "<br/>" 
    end 
end 
r unless r.blank? 
end 

结果：

• 直到行@issue.save一切看起来是正确的。我已检查@issue包含我所做的所有更改。
• 在用户界面上没有任何更改我已通知。
• 在日志中没有更新SQL是可见的。所有相关的选择和插入呈现，但没有更新 - 在表中，以便没有变化issues
• 甚至textalize_changes检查时为（changed?）
• 如果我手动更改属性在源代码还没有实现和对象的变化水平由name=XXX它工作。

我不知道要检查或检查什么。代码非常简单，我根本不知道。

下面是操作的日志：

original object 
    --- !ruby/object:Issue 
    attributes: 
     name: OTTO TEST 2 
     assigned_to: "29" 
     updated_at: 2010-12-16 10:25:28 
     project_id: "1" 
     current_estimate: 
     lft: "1" 
     original_estimate: 
     priority: 
     id: "10" 
     version_id: 
     area_id: 
     description: 
     worktype_id: "2" 
     status_id: "5" 
     rgt: "2" 
     parent_id: 
     created_at: 2010-05-21 07:37:15 
     fixed_in_version_id: 
    attributes_cache: {} 

    bulk attribute settings... 
    WARNING: Can't mass-assign these protected attributes: description 
     [4;36;1mIssue Load (0.0ms)[0m [0;1mSELECT "lft", "rgt", "parent_id" FROM "issues"  WHERE ("issues"."id" = 10) [0m 
    after bulk settings 
    --- !ruby/object:Issue 
    area: 
    assigned_user: 
    attributes: 
     name: qqqqqqqqqq 
     assigned_to: "29" 
     updated_at: 2010-12-16 10:25:28 
     project_id: "1" 
     current_estimate: 
     lft: "1" 
     original_estimate: 
     priority: 
     id: "10" 
     version_id: 
     area_id: 
     description: 
     worktype_id: "2" 
     status_id: "5" 
     rgt: "2" 
     parent_id: 
     created_at: 2010-05-21 07:37:15 
     fixed_in_version_id: 
    attributes_cache: {} 

    changed_attributes: {} 

    children: 
    events: 
    fixed_in_version: 
iterations: 
marked_for_destruction: false 
parent: 
project: 
status: 
timelogs: 
version: 
work_items: 
worktype: 
    [4;35;1mEvent Create (0.0ms)[0m [0mINSERT INTO "events" ("updated_at", "verb", "external", "issue_id", "note", "changes", "user_id", "created_at") VALUES('2010-12-16 10:33:08', 'Edited', 'f', 10, '', NULL, 1, '2010-12-16 10:33:08')[0m 
after save 
    [4;36;1mEvent Load (16.0ms)[0m [0;1mSELECT * FROM "events" WHERE ("events".issue_id = 10) ORDER BY id ASC, created_at ASC[0m 
--- &id001 !ruby/object:Issue 
area: 
assigned_user: 
attributes: 
    name: qqqqqqqqqq 
    assigned_to: "29" 
    updated_at: 2010-12-16 10:25:28 
    project_id: "1" 
    current_estimate: 
    lft: "1" 
    original_estimate: 
    priority: 
    id: "10" 
    version_id: 
    area_id: 
    description: 
    worktype_id: "2" 
    status_id: "5" 
    rgt: "2" 
    parent_id: 
    created_at: 2010-05-21 07:37:15 
    fixed_in_version_id: 
attributes_cache: {} 

技术信息：

• 操作系统：winXP的
• 导轨：导轨2.3.4

附加信息：

我有一个批量操作，它具有正常工作的相同用途。我真的不知道它们的区别：

def update_multiple 
if params['cancel'] 
    redirect_to issues_path 
    return 
end 
@issues = Issue.find(params[:issue_ids]) 
@issues.each do |issue| 
    issue.attributes= params[:issue].reject {|k,v| v.blank? } 
    issue.apply_template_on_name_change 
    issue.events.build(:note=>params[:issue][:description],:verb=>"Edited", :changes=>issue.textalize_changes) 
    issue.save! 
end 
flash[:notice]="Issues updated!" 
redirect_to issues_path 
end 

附加信息：

如果我更换@issue.attributes= params[:issue]通过@issue.attributes= params[:issue].reject {|k,v| v.blank? }它应用的变化和工作。但这不是我真正想要的。我想立刻改变一切。我快疯了。

Answer 1

我在超棒的嵌套集中发现了这个问题。

该插件在执行嵌套集合操作之前重新加载对象。：我通过以下方式更换了控制器：

@issue.parent_issue= params[:issue][:parent_issue] 
@issue.attributes= params[:issue].reject {|k,v| 'parent_issue'==k } 

这是现在最好的解决方案。

注意：parent_issue用于设置给定实体的父级，并使用与其余属性相同的形式。

Answer 2

您可以尝试使用感叹号保存，例如@issue.save!以查看错误。