我想更新表,但更新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? }
它應用的變化和工作。但這不是我真正想要的。我想立刻改變一切。我快瘋了。
您是否檢查過您的驗證或before_save過濾器? – 2010-12-15 11:41:52
Code segmen'if @ issue.save redirect_to(@issue)'會照顧這樣的事情。我已經檢查過這個成功案例。 (我已經使用記錄器和調試器來追蹤這些步驟,但仍然沒有更新操作) – takacsot 2010-12-15 15:18:00
我想強調一下'save'對象'@ issue'發生了變化。 (我可以打印出更改的屬性)。 ant方法'改變?'的響應也是錯誤的。 – takacsot 2010-12-15 15:30:17