This week's giveaway is in the Spring forum.
We're giving away four copies of Learn Spring Security (video course) and have Eugen Paraschiv on-line!
See this thread for details.
Win a copy of Learn Spring Security (video course) this week in the Spring forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Question for Dave Thomas/David Heinemeier Hansson

 
Max Tomlinson
Ranch Hand
Posts: 365
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
First of all, thanks for taking my question.

How does Rails propose to handle legacy data models moving forward? From what I've seen Rails really only works for new 'greenfield' applications, not ones that have complicated table structures with complex keys etc.

thanks
Max Tomlinson
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's actually not Rails which has trouble with composite keys etc. It's the ORM framework that Rails uses by default, ActiveRecord, which has the trouble. You are free to use raw SQL or an alternative ORM tool instead of ActiveRecord if it doesn't quite cut it in your environment.
 
Prag Dave
author
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Rails isn't intended to be a 100% solution: DHH's philosophy is to do the 80% really well, and leave the rest to stuff like Java.

Having said that, Rails plays really well with Web Services (and web services), and that provides a good integration point with the legacy world.


Dave
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic