similar to: Having trouble with update_attributes() after member access

Env. is samba-3.0.9-1.3E.10 on CentOS 3.7 as PDC with WXP SP2 clients. Situation: 1) a user receives notification at logon that the password is expiring and that only few days remain to change it 2) he/she answers yes and puts old and new passwords and press ok 3) the system sends the error message: authorization to change the password is missing (real message is in italian: "Manca

Hello again... so I narrowed my problem down. For some reason, while using login_generator, any User object I pull from the DB can be updated one attribute at a time using update_attribute, but when I try and do update_attributes it fails every time. Is this a limitation with login_generator that I don''t know about, or is there a way around this? I also tried the .update method and

I notice that ActiveRecord::Base.update_attributes() calls save(). What if I want to get an exception if the save fails? Is there a way to get the update_attributes() function plus the save! function? Thanks, Wes -- Posted via http://www.ruby-forum.com/.

I am trying to wrap the updating of two models in a transaction and when the transaction fails it is not rolling back. My method is : def update_attributes(user,params) @user = user @company = user.company begin User.transaction do @user.update_attributes!(params[:user]) @company.update_attributes!(params[:company]) end true rescue false

Hi! I have updated my app to rails 2.3. I have form that has few nested models and I am happy that I can just write accepts_nested_attributes_for :tasks, :allow_destroy => true, but update_attributes! does not update my nested model. I have tried update_attributes, and it works. Any ideas? Few lines from log: update_attributes: SQL (0.1ms) BEGIN Education Update (0.3ms) UPDATE

Hi, IN one of my unit tests I get an ActiveRecord::StaleObjectError: Attempted to update a stale object object.save! in object I have apart from other stuff an after_save method, which calls object.assosication.update_attributes(...) If I remove that line from my code my tests succeeds. Unfortunetly, I do not understand why an update_attributes call can generate an StaleObjectError. Maybe

Is it possible to update the parameters from a form without saving? @model.update_attributes(params[:model]) will save the model after updating its attributes. I''d just like the attributes updating without a save. Thanks Chris -- Posted via http://www.ruby-forum.com/.

Hi, I am facing a problem while trying to test a method that updates an attribute. The attribute format should be converted to YAML format before storing in the table which is excatly what is going on. But when testing it using expectations in rspec it returns an error. *** below is the error message : Spec::Mocks::MockExpectationError in ''InteractController (submit) - saving a form to

I dont know if its me or the dodgy win-32 intall of ruby/mysql, but I can''t seem to get update_attributes to work. In my user controller, I have: def update @user = User.find(@params[''user'']["id"]) if @user.update_attributes(@params["user"]) flash["success"] = "Updated Successfully" redirect_to :action =>

Hi all, I''ve searched the forumns, but I can''t seem to find an answer to this one. I''m having trouble getting optimistic locking (OL) to work in my app, even though all of the pieces are there: * table has lock_version column, with default of 0 (zero) * lock_version column is being incremented by the first update (but the second doesn''t catch it) *

Hi, I have one method, ''updateStuff'', that will call ''update_attributes'' on 3 different models in the DB..... How can I account for validation to revert back all updates if one of the models is not valid? I''ve looked into Model.valid? which doesn''t seem to work for me .. Any idea? Thanks

I know there have been threads on this before but I was thinking shouldn''t multiple collection_select automatically update habtm relations when you update_attributes? In order to get multiple collection_select to work I use: collection_select(:user, :group_ids, Group.find(:all), :id, :name,{},{:multiple=>'''',:name=>''group[id][]''}) In fact if I

shouldn''t @m.update_attributes(params[:m]) only update the attributes listed in the params hash? it tries to update all table attributes I hacked _form.rhtml and removed some of the fields, hoping that they will not be updated.. but it didn''t work.

Hi, Is it best to simulate errors in functional testing by stubbing the controller save/update_attributes to return false? Will I miss anything important if I always test controller behavior in the case of errors in this way? Thanks, Lille -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

I have two models. model A has_many :b def before_validation_on_create ......... end model B belongs_to :a In b''s controller and ''update'' action, I have a.update_attributes(params[ :a ]) So when I was trying to create a new ''b'', before_validation_on_create is being called twice. Pleas let me know if you guys have any suggestions. Thanks in

I''m working on a form that updates a product record and several associated detail records. The detail records are showing and populating okay in the form. But when it hits the controller, I get Couldn''t find Detail with ID=detail AND (details.product_id = 38). The :detail params seem to refer to the correct record id. Anyone have an idea how to fix this? Here''s the

Hope someone can tell me what''s up, because this has me baffled. I have an Image model, and a Provider model. Both are defined as "has_and_belongs_to_many" relating to each other. In my image form partial, I have a bit of AJAX generating the provider_ids array dynamically from a provider AJAX search on the same page. So for example, each time I click on a provider name that

I have a basic login system implemented. I''ve recently added a timestamp field "last_activity_time". During the login process, if I successfully get back a user object, I do this: user.update_attribute(:last_activity_time, Time.now()) It appears to be successful given the breadcrumbs I''ve strewn around it, but nothing gets written out to my table. In

In my User model, I had this: def update_last_login_time self.last_login = Time.now self.save end But last_login was not being set. When I changed it to this it worked: self.update_attribute( :last_login, Time.now ) Any ideas why? ~S

Hi there, I''ve asked this question at stackoverflow.com http://stackoverflow.com/questions/11257662/can-i-make-rails-update-attributes-with-nested-form-find-existing-records-and-ad I haven''t seen a better answer than one I propose myself but I''d like to know if it''s possible to enhance accepts_nested_attribute_for to allow a find_or_create_by behavior for