wood burning stoves*
The moose likes Ruby and the fly likes Agile Web Development with Rails: conventions & legacy systems Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Languages » Ruby
Bookmark "Agile Web Development with Rails: conventions & legacy systems" Watch "Agile Web Development with Rails: conventions & legacy systems" New topic
Author

Agile Web Development with Rails: conventions & legacy systems

Gian Franco
blacksmith
Ranch Hand

Joined: Dec 16, 2003
Posts: 977
Hello,

I'm not well versed Rails yet, but if I'm not
mistaken many of the advantages of Rails come
from strict conventions that allow the developer
to focus on...development.

Isn't it so that, for example database objects
naming conventions, might be too restrictive or
too renewing in existing systems? A DBA might
not be very open to such changes.

Kind regards,

Gian


"Eppur si muove!"
Aitor Imaz
Greenhorn

Joined: Jan 30, 2005
Posts: 8
The naming conventions are defaults for the most part. You can override them if you will, although you'll be losing a lot of what Rails gives you in terms of simplicity and productivity.

There are more things that can drive some DBAs nuts, like no composite keys (although I believe there are plugins that can let you use them). So yes, it's better suited for "new" applications.

Personally, I don't see it as a restriction, it's a feature. Rails doesn't claim to be the best tool for *any* job, but it's definitely the best tool for *many* jobs.
Eric Martinez
Greenhorn

Joined: Nov 20, 2005
Posts: 25
By following the conventions you get to harness some of the powerful Rails features that you might otherwise miss out on. As Aitor Imaz said, I do not see them as restrictions at all.
Gian Franco
blacksmith
Ranch Hand

Joined: Dec 16, 2003
Posts: 977
I agree with you that conventions harness some of
the powerful Rails features, but my point is not
that I would like to work with Rails just for the
sake of it.

If Rails is meant to improve ones productivity fine,
but how much momentum can it gain in an environment
where it's difficult to implement it's requirements
that will allow these productivity boosts?

It's back to 'there is no silver bullet', but then
again I'm still in need of more actual facts regarding
Rails and it's success.

Kind regards,

Gian
Prag Dave
author
Greenhorn

Joined: Feb 17, 2004
Posts: 24
Just about every convention in Rails can be overridden, so in theory you can always adapt to a legacy schema.

Having said that, there are times where this might get to be just too much of a pain. My advice would be to experiment with writing basic models that map any legacy schema you might be thinking of using, and seeing if it works, before comitting to the full application.
 
wood burning stoves
 
subject: Agile Web Development with Rails: conventions & legacy systems
 
Similar Threads
Why the Rails for Java guys ?
Performance Comparison of REST with Rails
Do models in Rails bother you?
Rails uptake time?
What is Rails ?