[typo] Moving to Latest SVN

gpshewan gpsnospam at gmail.com
Thu Oct 20 05:06:51 EDT 2005


The migration doesn't have a drop table function so if you had an  
aborted migration and it had already created the table - then the  
next time you try it'll choke (so you have the error).  Just delete  
the table 'tags' from the database and try the migration again.

On 19 Oct 2005, at 17:43, Phil Cryer wrote:

>
>
>>> BTW, I simply ran migrate and I was up and running.
>>> Granted, I had to specify the production environment, as dev is the
>>> default for rake's migrate task.
>>>
>>>
>>
>> ok, so I have the latest svn, 683 - how can I 'rake migrate' and
>> have it update my production db, or is there a better/more
>> recommended way to do it?  how did you do it, modify something in
>> the Rakefile?
>>
>
>
>> Try 'rake migrate RAILS_ENV=production'
>>
>
> Got farther, but bombed out with:
>
> [phil at pepe ~/websites/fak3r.com/typo]# svn update
> At revision 683.
> [phil at pepe ~/websites/fak3r.com/typo]# rake migrate  
> RAILS_ENV=production
> (in /usr/home/phil/websites/fak3r.com/typo)
> rake aborted!
> Table 'tags' already exists: CREATE TABLE tags (id int(11) DEFAULT  
> NULL auto_increment PRIMARY KEY, name varchar(255), created_at  
> datetime, updated_at datetime) ENGINE=InnoDB
> ./Rakefile:218
>
>
> http://fak3r.com - you don't have to kick it
>
> _______________________________________________
> Typo-list mailing list
> Typo-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
>



More information about the Typo-list mailing list