Databases
StackOverflow2013
Postsdbo
PO:autosave property of has_many associations broken in Rails 2.3.4?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO:autosave property of has_many associations broken in Rails 2.3.4?
    primarykey
    data
    text
    <p>Before I post this as a bug to the rails team, I wanted to see if I'm doing something wrong that may be causing this behavior. Specifically, the :autosave property of has_many associations doesn't seem to be working as per the docs.</p> <p>For reference, here is the most current API documentation: <a href="http://api.rubyonrails.org/classes/Acti" rel="nofollow noreferrer">http://api.rubyonrails.org/classes/Acti</a> … ation.html</p> <p>Take a look at the "One-to-many Example" section. I have duplicated the code there exactly in a test application, and it isn't working for me. Specifically, the parent object is updated, but the child object is not.</p> <p>My schema is as follows:</p> <pre><code>create_table :posts do |t| t.string :title t.timestamps end create_table :comments do |t| t.text :body t.integer :post_id t.timestamps </code></pre> <p>My models are as follows:</p> <pre><code> class Post &lt; ActiveRecord::Base has_many :comments, :autosave =&gt; true end class Comment &lt; ActiveRecord::Base belongs_to :post end </code></pre> <p>In the console, I run the following commands (the post and comments objects are already in the DB at this point):</p> <pre><code> post = Post.find(1) post.title # =&gt; "The current global position of migrating ducks" post.comments.first.body # =&gt; "Wow, awesome info thanks!" post.comments.last.body # =&gt; "Actually, your article should be named differently." post.title = "On the migration of ducks" post.comments.last.body = "Actually, your article should be named differently. [UPDATED]: You are right, thanks." post.save post.reload </code></pre> <p>But this is what I get for output:</p> <pre><code> post.title # =&gt; "On the migration of ducks" post.comments.last.body # =&gt; "Actually, your article should be named differently." </code></pre> <p>Further, looking in the logs this is the only update statement I see:</p> <p>Post Update (0.6ms) UPDATE "posts" SET "updated_at" = '2010-01-18 23:32:39', "title" = 'On the migration of ducks' WHERE "id" = 1</p> <p>So it appears that the save didn't cascade down to the comments object, which seems clearly broken to me. I have tried this on two different systems running 2.3.4 and the behavior is repeatable.</p> <p>Here's the weird part, though: If I first call "post.comments" before I try to set the value, it works fine! To be exact:</p> <pre><code> post.title = "On the migration of ducks" post.comments #Note that this line was not called above post.comments.last.body = "Actually, your article should be named differently. [UPDATED]: You are right, thanks." post.save post.reload </code></pre> <p>Now the output gives me the correct results:</p> <pre><code> post.title # =&gt; "On the migration of ducks" post.comments.last.body # =&gt; "Actually, your article should be named differently. [UPDATED]: You are right, thanks." </code></pre> <p>And the logs contain the correct update:</p> <p>Comment Update (0.3ms) UPDATE "comments" SET "updated_at" = '2010-01-18 23:44:43', "body" = 'Actually, your article should be named differently. [UPDATED]: You are right, thanks.' WHERE "id" = 2</p> <p>So this really looks broken to me. I'm guessing that it's a problem with the way that object references are handled, i.e. that once the object is part of an allocated collection it saves fine but does not save when it is pulled as a single object from the database. But before I submit this to the Rails team as a bug I wanted to see if anybody else had run into this issue, or if I'm just doing something completely boneheaded that I'm not seeing because I've spent all day on this.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Travers
    1. USmrjake2
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO:autosave property of has_many associations broken in Rails 2.3.4?
      1. USnioq
      1. VTFavorite
    2. VO
      singulars
      1. PO:autosave property of has_many associations broken in Rails 2.3.4?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO:autosave property of has_many associations broken in Rails 2.3.4?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't think you can post a bug for Rails 2.3.4, since that's not even the last stable release of the 2.3 series. It's possible there was a bug that was fixed in the AutosaveAssociation module. I would even doubt that they would make a bugfix to this in 2.3.11.
      singulars
      1. PO:autosave property of has_many associations broken in Rails 2.3.4?
      1. USBen Moss
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload