rake db:migrate issue postgresql

Question

I'm complete noob at PostgreSQL, Ruby on Rails..

I'm trying to follow this tutorial (WITHOUT rubymine) http://www.codeproject.com/Articles/575551/User-Authentication-in-Ruby-on-Rails#InstallingRubyMine4

I have as such this to migrate (001_create_user_model.rb):

class CreateUserModel < ActiveRecord::Migration
  def self.up
    create_table :users do |t|
      t.column :username, :string
      t.column :email, :string
      t.column :password_hash, :string
      t.column :password_salt, :string
    end
  end

  def self.down
    drop_table :users
  end
end

The error I'm getting goes like this:

syntax error, unexpected ':', expecting ';' or '\n'
        t.column...sers do |t|

...
C:131071:in 'disable_dll_transaction'
Task:TOP => db:migrate

that is some really old syntax you have there.... doesnt look like a good tutorial. — sevenseacat
– sevenseacat, Commented Sep 4, 2013 at 4:49
hmm, I tried the syntax below as well. Didn't work, same error. — Ahmad Bilal
– Ahmad Bilal, Commented Sep 8, 2013 at 19:17

Benjamin Tan Wei Hao · Accepted Answer · 2013-09-04 04:19:14Z

1

What about this:

class CreateUserModel < ActiveRecord::Migration
  def self.up
    create_table :users do |t|
      t.string :username, :null => false
      t.string :email,:null => false
      t.string :password_hash, :null => false
      t.string :password_salt, :null => false
      t.timestamps
    end
  end

  def self.down
    drop_table :users
  end
end

answered Sep 4, 2013 at 4:19

Benjamin Tan Wei Hao

9,6723 gold badges34 silver badges57 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Benjamin Tan Wei Hao Over a year ago

Besides the textual differences? I just picked out a random migration and converted it to that format. Not sure if Ahmad's migration is from an older version of Rails.

hawk Over a year ago

Not textual difference. His code is still valid according to ActiveRecord::Migration documentation. Your answer should be 'You can also use the column types as method calls, rather than calling the column method.' But it not solving the problem from code view.

Benjamin Tan Wei Hao Over a year ago

Worth a shot, FWIW. Besides, we don't have much to go on. :)

Collectives™ on Stack Overflow

rake db:migrate issue postgresql

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related