On 15 March 2010 18:14, Greg Donald <[email protected]> wrote: > On Mon, Mar 15, 2010 at 12:18 PM, Aldric Giacomoni <[email protected]> > wrote: >> What possible benefit could you derive from this > > A second table is required when you have constraints that you don't > want interfering with your ability to save data to the first table. > has_one is very useful for this scenario.
I can't tell what your angle is from this post - are you disagreeing with Aldric, or the OP? A has_one is the association the OP said he didn't want; and the idea of a second table with no association is what Aldric seems to be querying. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
