Well, the updated_at timestamp for the album should update automatically 
to the current time whenever the album model is changed and saved, so if 
you're trying to do that then you don't need to use touching.

I'm confused at how your app is set up - if album has_many photos and 
photo belongs_to album, then shouldn't your photo saving method use 
singular objects? As in:

@photo.album.updated_by = @currentusername
@photo.album.save

That is, assuming you've defined "updated_by" in your migration as a 
string to save the name of the current user - I think that's what you're 
going for.

What I would do next is put debugger right between those two lines, then 
call the save as a bang method (@photo.album.save!) and see what error 
you get (if any).

Chris



Carlos Santana wrote:
> Thanks Chris.
> I am using created_at and updated_at attributes for timestamps. For 
> getting user info. though, I have creuser and upduser attributes.
> 
> Is there any other way to do this other than upgrading it to edge rails?
> 
> Thanks,
> CS.
> 
> Chris Hanks wrote:
>> I think the new functionality in edge rails will do what you want:
>> 
>> http://afreshcup.com/2009/04/19/touch-your-active-record-instances/
>> 
>> You say:
>> 
>> class Photo
>>   belongs_to :user, :touch => true
>> end
>> 
>> This way, whenever you save or delete a photo instance, it'll 'touch' 
>> its parent user, and update the updated_at timestamp.
>> 
>> This will require you to upgrade to edge rails, though.
>> 
>> Looking at your attempt, though, I'm not sure this is what you want. Are 
>> you also using the "updated_by" attribute of the photo to save the id of 
>> the user that changed it?
>> 
>> Chris
>> 
>> 
>> 
>> 
>> Carlos Santana wrote:
>>> I have nested resources as follows: 'albums has_many photos'.
>>> Whenever someone edits photos, I would like update time stamp on albums.
>>> I tried to do this like:
>>> @photos.albums.updated_by = @currentusername
>>> @photos.albums.save
>>> 
>>> But, this is not updating albums. I don't see anything happening in the
>>> database log or mongrel log.
>>> 
>>> -
>>> CS.

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
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 [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to