Injecting Rails into your Legacy World 6
Many of you know that I have an unhealthy obsession with databases… in particular legacy databases. I’m not the only one it seems. :-)
I’m hoping to compile a few stories of how Rails enthusiasts have been able to take advantage of the Ruby on Rails framework within a Legacy environment, whether that be to talk with legacy databases, web services, or a piece of cauliflower. If you have a story (good or bad) of how you used Rails with a legacy system, please email me and let’s talk. :-)
Also, I would like to announce that I have started a new google group that focuses on the topic of using Rails with legacy environments. Check out the new Rails and Legacy group.
If you’re down in California, you can see my talk, “Rails meets the Legacy World” at the Ruby on Rails Seminar, which is being hosted at the AJAXWorld Conference & Expo.
Enjoying the content? Be sure to subscribe to my RSS feed.
If you’re interested in Rails + legacy databases, please check out Jon’s rBatis
I do work with a legacy database (an anti-Ror one as I like to call it: no auto-incremented id, singular table names, CamelCased column name and so on..) .. I do write some preliminary stuff here: http://sl33p3r.free.fr/tutorials/rails/legacy/legacy_databases.html, but juste rewrote completely the interface between Rails and my legacy database: now code follow rails convention but databse follows anti-Ror conventions.
I do work with a legacy database (an anti-Ror one as I like to call it: no auto-incremented id, singular table names, CamelCased column name and so on..) .. I do write some preliminary stuff here: http://sl33p3r.free.fr/tutorials/rails/legacy/legacy_databases.html, but juste rewrote completely the interface between Rails and my legacy database: now code follow rails convention but databse follows anti-Ror conventions.
I do work with a legacy database (an anti-Ror one as I like to call it: no auto-incremented id, singular table names, CamelCased column name and so on..) .. I do write some preliminary stuff here: http://sl33p3r.free.fr/tutorials/rails/legacy/legacy_databases.html, but juste rewrote completely the interface between Rails and my legacy database: now code follow rails convention but databse follows anti-Ror conventions.
test
I immediately thought of the ibatis port. I’ve read about this a few times, but was wondering if anyone is actually using it? There are some database structures so obtuse (and unfortunately I’ve inherited one) that no amount of overriding to trick rails will work. rbatis could be the trick though? If you’re using, please comment if the magic works.