<div dir="ltr">It's historical. When Rails was first minted, you could hook it up to a MySQL database, drop a scaffold tag in your view, and Rails would dynamically compose the front end for you. One of the killer features was that you could reorder the fields in your mySQL table using some GUI and the forms would update automagically. <div><br></div><div>All that is long since gone, but the pattern remains, Rails will infer model fields based on your DB schema.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 25 February 2015 at 17:28, Rory Sinclair <span dir="ltr"><<a href="mailto:rory@asmallworld.net" target="_blank">rory@asmallworld.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-family:Helvetica;font-size:13px">Enrique Riepenhausen did a really good talk on this subject at Scottish Ruby Conf in 2011. He touched on this quite a bit, as well as the mindset we tend to get into 'translating' our customers language into CRUD operations we can do on AR objects, which is, he argues, a bit too low-level and not really modelling the domain at all. It certainly stuck with me since, and i've tried to apply it to stuff I build (though i'm not dealing with AR directly every day these days).<div><br></div><div>Here's the link, but unf. the video doesn't seem to be working at the moment, and I couldn't find a working one... :(</div><div><br></div><div><a href="http://confreaks.tv/videos/scotlandruby2011-don-t-build-another-tower-of-babel" target="_blank">http://confreaks.tv/videos/scotlandruby2011-don-t-build-another-tower-of-babel</a></div></div><span class="HOEnZb"><font color="#888888">
<div><div><br></div><div>-- </div><div>Rory Sinclair</div><div>Head of Technology</div><div>ASMALLWORLD</div><div><br></div></div></font></span><div class="HOEnZb"><div class="h5">
<p style="color:#a0a0a8">On Wednesday, 25 February 2015 at 16:51, Thomas Buckley-Houston wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div><div>Really interesting to hear the viewpoint that AR is just a persistence</div><div>layer and not designed to define the domain model. It all makes a lot</div><div>more sense now.</div><div><br></div><div>@jc I'm interested in your idea about using accessors for each</div><div>attribute, I'd like to try that. But yes, it's still not the single</div><div>source of truth and so there's the risk of going out of sync with the</div><div>DB.</div><div><br></div><div>Anyway, lots to think about, much appreciated folks :)</div><div>_______________________________________________</div><div>Chat mailing list</div><div><a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a></div><div>Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a></div><div>Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a></div><div>List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>
</div></div><br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote></div><br></div>