If it is a "baby name chooser" application then each "name" needs to know whether the name can be "male", "female" or "both." I would create male? and female? as separate fields that can be either true or false. This simplistic approach to design is superior to creating a both option in one field.
On Thu, Jul 29, 2010 at 11:03 AM, bingo bob <li...@ruby-forum.com> wrote: > Thanks chaps. > > It's now got me thinking. This stuff is not as easy as it looks. Ive > given up on gender when I realised that a name can belong to both > genders! > > In English my app is a baby name chooser > > A baby can have many proposed names but only one surname. > > A name can be of many types, forename / middlename etc > > Any tips how to model this! > > -- > 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-t...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com<rubyonrails-talk%2bunsubscr...@googlegroups.com> > . > 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 rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
