Kristan Uccello wrote:
Yes I did: trace below
r...@oa-radiant-devsite:~/oa-dev-site# rake production db:bootstrap
(in /root/oa-dev-site)
This task will destroy any data in the database. Are you sure you want to
continue? [yn] y
that sure looks fine... any chance that you're running Radiant in
d
Yes I did: trace below
r...@oa-radiant-devsite:~/oa-dev-site# rake production db:bootstrap
(in /root/oa-dev-site)
This task will destroy any data in the database. Are you sure you want
to
continue? [yn] y
== AddIndexes: reverting
=
-- rem
Did you bootstrap the database? If so, did you bootstrap the correct
one? It's likely that your application is running in a different
environment than the one you bootstrapped.
rake production db:bootstrap
Sean
Kristan Uccello wrote:
Thanks Jim for the last bit of info on ruby 1.9 incompata
Kristan Uccello wrote:
Thanks Jim for the last bit of info on ruby 1.9 incompatability.
I created a new cloud server and installed ruby 1.8.7 + rails +
sqlite3 etc. Now I have an issue logging in:
sorry if this is silly, but did you run the bootstrap script?
Cheers,
Mohit.
9/15/2009 | 3:17 AM
Thanks Jim for the last bit of info on ruby 1.9 incompatability.
I created a new cloud server and installed ruby 1.8.7 + rails +
sqlite3 etc. Now I have an issue logging in:
Here is what I get
ActiveRecord::StatementInvalid in Admin/welcomeController#login
Could not find table 'use
