• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Tim Cooke
  • Paul Clapham
  • Devaka Cooray
  • Bear Bibeault
  • Junilu Lacar
  • Knute Snortum
  • Liutauras Vilda
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Piet Souris
  • salvin francis
  • Carey Brown
  • Frits Walraven

Question for Dave Thomas/David Heinemeier Hansson

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.

Max Tomlinson
Posts: 11962
  • 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.
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.

This tiny ad is guaranteed to be gluten free.
Two software engineers solve most of the world's problems in one K&R sized book
    Bookmark Topic Watch Topic
  • New Topic