That would require having competing ORMs (rails plus whatever library or ad-hoc we roll in the new code) working against the same database. Unfortunately, it's

That would require having competing ORMs (rails plus whatever library or ad-hoc we roll in the new code) working against the same database. Unfortunately, it's a pretty complex system, and the changes we have slated don't really leave room for updating one endpoint at a time. Even if it were simpler, I don't recall anyone ever contemplating having two ORMs running against the same database without a shudder of horror.