Hi Jim, I wouldn't recommend storing a single object in two tables or splitting it across multiple rows. You'll be fighting this complexity elsewhere in your code and it will become a real headache.
Are you including images or something in your object? If so, you'd be much better off attaching them to your object with something like Paperclip (http://github.com/thoughtbot/paperclip/tree/master). This will just add a reference to the file to your object and store the data elsewhere (filesystem or Amazon S3). The filesystem is much better at storing large amounts of data than the database. Amazon S3 doesn't take much more effort to set up and has the advantage of making your attachment available across multiple servers that don't share the same filesystem. - Bill --~--~---------~--~----~------------~-------~--~----~ 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@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 -~----------~----~----~----~------~----~------~--~---
