I have a model Report, and a model ReportComponent. ReportComponent belongs to Report, and Report has_many components. Both tables have some commons fields such as organization_id, manager_id etc, and of course their own unique fields. There is no hard business reason for having these duplicate fields, but they help with join queries and DB performance. The issue i have is that I would like for ReportComponent to automatically pull organization_id from Report on creation, and store that in its own field. Not the same as ''AR#delegate'' as this would copy and write the field. Best idea i have right now is to override the organization= method, but that is not foolproof. Is there a native rails method for this? Thanks, -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/groups/opt_out.
On 18 February 2013 22:51, masta Blasta <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote:> I have a model Report, and a model ReportComponent. ReportComponent > belongs to Report, and Report has_many components. Both tables have some > commons fields such as organization_id, manager_id etc, and of course > their own unique fields. There is no hard business reason for having > these duplicate fields, but they help with join queries and DB > performance.Don''t repeat the fields, that is not good. Can you explain why you need them? There will almost certainly be a better way. Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/groups/opt_out.
Colin Law wrote in post #1097732:> On 18 February 2013 22:51, masta Blasta <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: >> I have a model Report, and a model ReportComponent. ReportComponent >> belongs to Report, and Report has_many components. Both tables have some >> commons fields such as organization_id, manager_id etc, and of course >> their own unique fields. There is no hard business reason for having >> these duplicate fields, but they help with join queries and DB >> performance. > > Don''t repeat the fields, that is not good. Can you explain why you > need them? There will almost certainly be a better way. > > ColinMost commonly is to make our jobs easier when analyzing the DB data. JOIN queries become a bit simpler. Yes it slightly defeats the purpose of a relational database, but we haven''t had any issues so far. Just the convenience of having those variables available right away is enough to bend some of the rules. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/groups/opt_out.