while trying to add a column through a migration. Searching Google took me to a couple of places, but it took a while to find a result that explained how to resolve this issue.
Luckily I came across this post by Mark Cornick, which explained that the issues was caused by the version of SQLite3 that is included in OS X 10.4.
After downloading and installing (from source) the latest version of SQLite3, and uninstalling and reinstalling the sqlite3-ruby gem
sudo gem install sqlite3-ruby
I was able to run the migration to add the column and continue on.






March 9th, 2007 at 8:48 pm
Thanks! This was driving me crazy.
March 9th, 2007 at 8:56 pm
Hi Eddie,
No problem. I’m glad my experience has been useful.
April 1st, 2007 at 5:23 am
…and an other guy who says thank you ’cause he was “driven crazy”
October 4th, 2007 at 8:45 am
Thanks!!! I spend 2 hours, and i find the solution thanks to you!
September 10th, 2008 at 3:51 am
I accidentally installed a version of sqlite over the top of my system’s one. I’m on OS X 10.4 and it has pretty much broken most of the applications (I think they all use CoreData which uses some of the sqlite libs). Does anybody have any ideas for how I can restore the original version without a complete reinstall of the OS?
I believe that the OS X 10.4 version comes with a patched version of sqlite 3.1.3. Perhaps I could obtain that from somewhere? I have hunted high and low on the Internet with no luck.
Any ideas welcome!!
October 8th, 2008 at 7:01 pm
I installed the last sqlite3 version via macports but continued getting that error. Until I read your sentence: “reinstalling the sqlite3-ruby gem”.
Thanks!