Rails update attributes not updating dating game show 1990s
This method will change the attribute in the model and pass it straight to the database, without running any validations.Two gotchas: this method also saves other changed attributes to the database.This is especially useful for boolean flags on existing records.The regular update_attribute method in Base is replaced with this when the validations module is mixed in, which it is by default.This is especially useful if you want to persist the changed class in your database.Note: The old instance's sti column value will be changed too, as both objects share the same set of attributes.I had to update the "_params" method to add it to the allowable list.user1 = User.create(name: "user1_name", email: "[email protected]", password: "foobar", password_confirmation: "foobar") user2 = User.create(name: "user2_name", email: "[email protected]", password: "foobar", password_confirmation: "foobar") msg1 = Message.create(sender_id: user1.id, receiver_id: user2.id, subject: 'subject_msg1', body: 'body_msg1') [email protected] = Message.find(msg1.id) @m.update_attributes(read_at: Time.now) For sure I'm missing something here, but I can't see where it is after changing and rechanging the has_many and the belongs_to from the associations, because I did put the read_at over the attr_accessible list HELP! Use attr_accessible to prevent mass assignment (by users) of attributes that should not be editable by a user.
update_attribute uses save(false) while update_attributes uses save (which means save(true)).
if so - rails will never add that field to the attributes using update_attributes. All, I had recently begun rails and was taking over someone else's code and found another scenario that was not covered here that was getting me.
When using the style pointed to by this link, the params are formed in a separate method.
reload rescue Active Record:: Record Not Found # If the record is gone there is nothing to do. If the model is new, a record gets created in the database, otherwise the existing record gets updated. If any of them fail the action is cancelled and save returns Saves the model. If any of them fail Active Record:: Record Invalid gets raised, and the record won't be saved. Attributes marked as readonly are silently ignored if the record is being updated. If no time argument is passed, the current time is used as default.
If the model is new, a record gets created in the database, otherwise the existing record gets updated. However, if you supply the action is cancelled and save!