File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Ruby and the fly likes Question for Dave Thomas/David Heinemeier  Hansson Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Languages » Ruby
Bookmark "Question for Dave Thomas/David Heinemeier  Hansson " Watch "Question for Dave Thomas/David Heinemeier  Hansson " New topic

Question for Dave Thomas/David Heinemeier Hansson

Max Tomlinson
Ranch Hand

Joined: Jul 17, 2001
Posts: 365
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.

Max Tomlinson
Lasse Koskela

Joined: Jan 23, 2002
Posts: 11962
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.

Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Prag Dave

Joined: Feb 17, 2004
Posts: 24
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.

I agree. Here's the link:
subject: Question for Dave Thomas/David Heinemeier Hansson
It's not a secret anymore!