Comments on: ActiveRecord behaviour with associations http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/ Hobo - the web app builder for Rails Sat, 12 May 2012 20:31:28 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Chris Apolzon http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/comment-page-1/#comment-51933 Chris Apolzon Thu, 03 Jun 2010 17:27:53 +0000 http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/#comment-51933 <p>Another great ruby skills post! I hope we can expect more of these in the future (obviously when yall have more time and ant busy with actually working on the hobo codebase)</p> <p>Articles like this are what ruby/rails needs to lower the barrier of entry for newcomers.</p> Another great ruby skills post! I hope we can expect more of these in the future (obviously when yall have more time and ant busy with actually working on the hobo codebase)

Articles like this are what ruby/rails needs to lower the barrier of entry for newcomers.

]]> By: Ara Vartanian http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/comment-page-1/#comment-48888 Ara Vartanian Sun, 05 Oct 2008 16:22:06 +0000 http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/#comment-48888 <p>Thanks Tom.</p> <p>Yeah, this is one of the things that drives me crazy about Rails and ActiveRec. I don't like the fact that DB calls happen silently in the background (and therefore fail silently in the background). There have been a couple of times where I've had tables messed up with half-formed object graphs on account of it.</p> <p>It gets even better with the #build series of methods, where you can associate to a collection without any save at all. My only problem with #build is that it only allows me to pass in attributes for a new objects rather than to assign an existing object and postpone the save for later.</p> Thanks Tom.

Yeah, this is one of the things that drives me crazy about Rails and ActiveRec. I don’t like the fact that DB calls happen silently in the background (and therefore fail silently in the background). There have been a couple of times where I’ve had tables messed up with half-formed object graphs on account of it.

It gets even better with the #build series of methods, where you can associate to a collection without any save at all. My only problem with #build is that it only allows me to pass in attributes for a new objects rather than to assign an existing object and postpone the save for later.

]]> By: Joe Van Dyk http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/comment-page-1/#comment-33574 Joe Van Dyk Mon, 05 May 2008 20:48:11 +0000 http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/#comment-33574 <p>http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html has details on when things are saved. </p> <p>Look down in the "Unsaved objects and associations" section.</p> http://api.rubyonrails.org/classes/ActiveRecord/Associations/ClassMethods.html has details on when things are saved.

Look down in the “Unsaved objects and associations” section.

]]> By: solars http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/comment-page-1/#comment-32937 solars Wed, 30 Apr 2008 06:13:32 +0000 http://hobocentral.net/blog/2008/04/29/activerecord-behaviour-with-associations/#comment-32937 <p>Thanks for the nice writeup Tom :)</p> <p>I remember there was only little information about when things get saved, back when I started with rails.</p> Thanks for the nice writeup Tom :)

I remember there was only little information about when things get saved, back when I started with rails.

]]>