Tag Archives: up

DB: the solution of table already exist when migrating

        When running rake DB: migrate, you sometimes find an error in rake abort. Rake says that a table already exists, so it can’t do the work of this migrate. This table does exist, so how can rake skip this table or force it to be overridden?There is one area that needs to be modified:

Original migrate file:

Ruby code

 

    class   CreateProducts  & lt;   ActiveRecord::Migration      def   self.up        create_ table  : products   do  | t|          t.column  : title,  : string          t.column  : description,  : text          t.column  : image_ url,  : string        end      end        def   self.down        drop_ table  : products      end    end   

    Modified migrate file:

    Ruby code

     

      class   CreateProducts  & lt;   ActiveRecord::Migration      def   self.up        create_ table  : products,  : force  =& gt;   true   do  | t|          t.column  : title,  : string          t.column  : description,  : text          t.column  : image_ url,  : string        end      end        def   self.down        drop_ table  : products      end    end   

      Do you see that in create_ In the parameter of table, add: force = & gt; True.

ERROR 0210: Stuck Key 36

Saturday, December 28, 2002 at 12:02 am
Windows Me Annoyances Discussion Forum
Posted by Jack Gulley (5917 messages posted)

This is a system board POST/BIOS error code (nothing to do with Windows). The ERROR 210: is a standard POST (Power On Self Test) error message that indicates an error with the keyboard. The error condition is that a keyboard scan code was received from the keyboard when none was expected, after the keyboard was Reset. The “Stuck key 36” indicates that scancode 36 was received, indicating that the Right Shift key was stuck down or was pressed when it should not have been.
If this occurs most of the time when you power on your system, then it indicates that this key is sticking down or the key mechanical or electrical parts are broken. Some times blowing out and cleaning out around the keys will resolve this problem. Some times holding the keboard vertical with the front edge down and droping several inches will clear up the problem. Otherwise, you need to replace your keyboard with a new (or at least a working) one.