Forum: Ruby on Rails Migration Strategy (Reverse Engineering) Existing Database

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
0903bef4c65e20289c5cd9de8c70f125?d=identicon&s=25 BrendanC (Guest)
on 2007-03-23 19:40
(Received via mailing list)
What is the optimum strategy for getting started/reverse engineering
an existing (SQL Server) database for ROR development.

Can I reverse migrate (??terminology??) from an existing production
database and have all the foreign keys/database constraints/table
relationships recognized and get models and controllers generated
correctly?  (I can rename the exisiting Primary Table keys to match
the ruby conventions (e.g.  id etc.)) if that will help).

I'd like to avoid any hand coding (e.g. tweaking FKs/relationships)
as part of this initial migration. Once the migration is complete I
plan to use ROR to control any future changes - so this is a one time

Any links to tutorials/etc would be appreciated here.


This topic is locked and can not be replied to.