On Thu, Nov 11, 2010 at 1:20 PM, David Kahn <[email protected]> wrote:
>
>
> On Thu, Nov 11, 2010 at 12:14 PM, Brian Troutwine <[email protected]>
> wrote:
>>
>> On Thu, Nov 11, 2010 at 1:05 PM, Dani Dani <[email protected]> wrote:
>> > Marnen Laibow-Koser wrote in post #960765:
>> >>
>> >> Associate each record with a company.
>> >>
>> >>>
>> > Thank you Marnen. So it means each record should have an extra field to
>> > associate a record with a certain company. I had this also in mind, but
>> > I thought there are other better ways than this.
>> >
>> > Any more Ideas ?
>>
>> That's really the only sane way of doing things. If you're thinking
>> about modeling data in a database hot-dogging without putting your
>> data into a normal-form should be done with a really, really good
>> reason (and most times not even then).
>
> Not that I have experience with this, but I guess going the non-relational
> route you would not have to 'associate' data the way we think of it but in
> the end you still are doing it logically.... again, something to be done for
> good reasons as there would be costs and benefits to this route.

Oh, sure. One great reason for going the non-relational route is high
volume traffic on your data store. Updating and reading all those
pretty referential links does incur overhead, which some products can
ill afford to pay. Folks using Redis often end up building some of the
referential data that they need by hand. More possibility for bugs[1],
but, if you take care and _know_ certain properties of your data will
never need to be queried, better performance in some cases.

Normal form by default with plans to strip away NF criteria as needed
is good rule of thumb. Rather reminds me of the carpenter adage: "It
is easier to cut than to add some on."

1. DataMapper takes this pain away.

>>
>> Cheers,
>> Brian
>>
>> > Dani
>> >
>> > --
>> > 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 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.
>> >
>> >
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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.

Reply via email to