Älphä Blüë wrote: > I'll look into relational database design. Can you suggest a good book > to read? Or a good article perhaps?
I strongly, strongly recommend Enterprise Rails by Dan Chak. The basic philosophy behind it is that for a successful site, your data (and therefore your database) will outlive the Rails application on top of it. So a great deal of discussion (about half the book) is given over to creating a solid and resilient data foundation, and then getting Rails to interact with it in a seamless manner. I'm convinced the advice in this book has saved me from myself many times with Rails. You're probably using MySQL, and the book covers Postgres, but it sounds like you're still early enough that switching over won't be much of a hassle. And it'll really pay off later. Anyway, a good chunk of the book is on Google Books, so feel free to page through it a bit. http://books.google.com/books?id=thTju-4duY4C&pg=PP1&dq=enterprise+rails&ei=8gBDSrrsEoLGlQTQnJX8Dg -- 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 -~----------~----~----~----~------~----~------~--~---
