Re:7 reasons I switched back to PHP after 2 years on Rails -...
by tyler on Sunday September 23, 2007 @01:59AM
(#58477)
Its really not as bad as you might guess. It takes some time up front to go through each model and tell it what the actual table name is, what the actual primary key is, and etc.
Once that is complete though, its pretty much Rails business as usual.
This might not be practical for all applications. But, in looking at CDBaby, I would find it hard to believe that their data is all that complex.
It sounds like he was trying to using Rails to retrofit on to an existing PHP DB schema, which is an obvious nightmare and probably a stupid idea in the first place.