I’m trying to replicate this, but at the moment I’m having a problem running at all with an SQLite3 db: I just get an Invalid Table Structure error - not sure why, because I’ve used SQLite3 with Locomotive before.
I’ll look into it a bit, but as you may have seen, we might have another method for providing all-in-one installations of Tracks, so hopefully, we won’t have to deal with this kind of problem much longer
bsag,
I wouldn’t spend any additional time on this for my sake. I’ve been able to install everything proper and get it all running. I look forward to the slingshot dist.
Hello, I don’t know if you’ll remember me but I submitted a couple patches probably two years ago, I’m finally getting back to helping out a bit.
I tried two installs today, both with the trunk. The Ubuntu/Apache/Mongrel Cluster with Sqlite3 worked just fine.
The Debian etch on a usb drive using Webrick gives the same error as this thread. My auth scheme is definitely ‘database’. In user.rb it’s trying to compare ‘database’ to :
To fix it I removed the ‘libsqlite3-ruby1.8’ package from my machine so it would just use the version I installed through gem. This generated the correct schema.rb.
I also found one other small error, I would make a ticket but the guest user doesn’t seem to have new ticket privileges. I’ve attached a fix for when you’re rolling back versions.
To verify do a rake db:migrate VERSION=0 (note: this will DESTROY all your data!), it’ll fail with wrong arguments for remove_column. This patch should fix it:
FWIW, you’re having multiple versions of sqlite3-ruby. I’ve seen reports on other gems where that caused conflicts. Perhaps you can uninstall older versions ?