Assuming that Rails is still interacting with the DB, and the ID in question is the primary key (ie, the 'id' on the 'twits' table) isn't quite that easy.
I had to do this a couple of years back when I realized I had a table that'd grow quickly:
I'm actually interested in this answer as well. I know of a company using a proprietary db and now that their growth has literally exploded, they're stuck with it.
There, fixed, send check for $20 to donations@redcross.org
Call me back when they reach 18446744073709551615