Thanks, James, I am restarting the DJ process each time and see the changes to the worker code. I can in fact update the attribute with no problem via the console.
I've narrowed the problem down to something very strange. If I do this in the job worker: person.update_attributes(:subscription => 'None') it doesn't get updated and the SQL UPDATE statement doesn't include subscription. But if I do this: person.update_attributes(:subscription => 'none') # Or 'NONE' or 'Foo' or 'BelindaCarlisle' it works. So what's not to like about the word 'None'? There is nothing in the model, the callbacks, validations, etc. that I can find that would prevent this specific value from being written. I thought perhaps it was an issue with acts_as_audited not liking 'None' but since I can update the record from the console, and that update triggers the audit, I've discounted that theory. Very strange indeed. Time to google some more. Chris On Mar 18, 8:08 am, James Miller <[email protected]> wrote: > Are you restarting the delayed_job worker after any changes to your app? DJ > loads your app as it exists when the worker starts -- even in development. > > What does your delayed_job method look like? Can you update the attribute > without issues from the console? -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby To unsubscribe from this group, send email to sdruby+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
