hi folks, i''d like some advice about how to approach this database "problem". i have a website that sells products that are customizable, and are organized in lists. i can''t give the details of the actual product, but i''ll offer this baby clothes analogy: happy hat(tm) beanie: fuzzy ball => true, pattern => striped, color => [blue, white] angry feet(tm) shoes: color => white, laces => fat pretty okay(tm) shirt: material => lead the clothes are customized and saved in "outfits" created by users. my question is: should i create database tables for each user-created outfit? that seems like it would get out of hand. is there a better way? -- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
how long do the outfits need to be retained? do they need to be saved only until the user places an order/ reorders the product? are you planning to save the outfits for reporting? On May 14, 1:03 pm, browner than u <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> hi folks, > > i''d like some advice about how to approach this database "problem". i > have a website that sells products that are customizable, and are > organized in lists. i can''t give the details of the actual product, but > i''ll offer this baby clothes analogy: > > happy hat(tm) beanie: fuzzy ball => true, pattern => striped, color => > [blue, white] > angry feet(tm) shoes: color => white, laces => fat > pretty okay(tm) shirt: material => lead > > the clothes are customized and saved in "outfits" created by users. my > question is: > > should i create database tables for each user-created outfit? that seems > like it would get out of hand. is there a better way? > -- > Posted viahttp://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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
thanks for the reply guys. the outfits would be retained for long periods of time (~6 months or so). lvizon wrote:> how long do the outfits need to be retained? do they need to be saved > only until the user places an order/ reorders the product? are you > planning to save the outfits for reporting? > > On May 14, 1:03�pm, browner than u <rails-mailing-l...@andreas-s.net>-- 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---