Brian
2008-Apr-28 22:12 UTC
[Backgroundrb-devel] update_attribute overwrites existing attributes with NULL.
Hmm. When using update_attribute from within a worker method, it seems that Backgroundrb inserts null values into all attributes that are not explicitly set. Is this possible/true?
Brian Morearty
2008-Apr-28 22:45 UTC
[Backgroundrb-devel] update_attribute overwrites existing attributes with NULL.
Hi Brian, I''m not sure but perhaps this is the answer to your question? http://lists.rubyonrails.org/pipermail/rails/2006-May/039493.html Summary: put a :select on your "find" call so it only updates the attributes that were selected. (Not a backgroundrb issue, but an ActiveRecord one. Seems like an ActiveRecord deficiency to me. The link above is pretty old. Not sure if it''s fixed nowadays.) - Brian (not you) On Mon, Apr 28, 2008 at 3:12 PM, Brian <theeuniv at gmail.com> wrote:> Hmm. > > When using update_attribute from within a worker method, it seems that > Backgroundrb inserts null values into all attributes that are not explicitly > set. Is this possible/true? > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080428/3cf03681/attachment.html>