Quick note: we just pushed a fix to this to the Gitorious mainline:
http://gitorious.org/gitorious/mainline/commit/1044ff0339055857c97377f9ec113469e6dc03f6
http://gitorious.org/gitorious/mainline/commit/1044ff0339055857c97377f9ec113469e6dc03f6The
commit message describes what happened here. This
I can confirm that this works. It's actually faster as well.
On Tuesday, March 1, 2011 2:14:46 PM UTC+1, Marcin Olak wrote:
Instead of migrating try to load schema directly:
rake db:schema:load RAILS_ENV=production
On 27 Lut, 19:46, Ryan Gibbons insani...@gmail.com wrote:
I had the
Instead of migrating try to load schema directly:
rake db:schema:load RAILS_ENV=production
On 27 Lut, 19:46, Ryan Gibbons insanity5...@gmail.com wrote:
I had the same problem I got around it by migrated like this .. it's hack
and I make no guarantees you will have a working system when it's
I got the same error, here is my walkaround:
After the first time you get the error, run the following statements
with mysql:
alter table projects add suspended_at datetime;
alter table projects drop owner_id;
alter table projects drop owner_type;
(The last 2 lines are necessary, or
I got the same error, here is my walkaround:
After the first time you get the error, run the following statements
with mysql:
alter table projects add suspended_at datetime;
alter table projects drop owner_id;
alter table projects drop owner_type;
Then run db:migrate again (The last
I had the same problem I got around it by migrated like this .. it's hack
and I make no guarantees you will have a working system when it's down, but
it should be okay :/
*Option 1*
export RAILS_ENV=production
rake db:migrate VERSION=20090203101718
then go into database and add a column to
I don't know what is causing this error, but I can confirm it as being
introduced in a425f3b.
If you want to continue with your install, run git checkout 63051e0.
Max
On Feb 25, 12:15 am, ssdowd ssd...@gmail.com wrote:
I get the following when trying to run a db:migrate (first time):
(ubuntu
