unsigned int field in a Ruby on Rails migration?

Question

How could I make population unsigned?

  def self.up
    create_table :cities do |t|
      t.string :name
      t.integer :population
      t.float :latitude
      t.float :longitude

      t.timestamps
    end
  end

FYI, you should now just be able to pass `unsigned: true` to that line and it will make the `integer` unsigned. — Joshua Pinter, Oct 14 '21 at 15:24

rwilliams · Accepted Answer · 2010-11-11T16:48:52.910

31

This should work for you.

t.column :population, 'integer unsigned'

edited Nov 11 '10 at 16:48

answered Nov 11 '10 at 16:43

rwilliams

21,188
6
49
55

score 7 · Answer 2 · answered May 23 '11 at 12:57

7

Just to add one more thing. This works perfectly. But need to note that it will make the migration code database dependent.

answered May 23 '11 at 12:57

Indika K

1,332
17
27

score 2 · Answer 3 · answered Nov 23 '13 at 09:02

2

step 1:

add activerecord-mysql-unsigned to GemFile

# add unsigned integer support to mysql2 adapter
gem "activerecord-mysql-unsigned", "~> 0.0.1"

step 2: install gems

bundle install

step 3:

use "unsigned: true" in fields you like

t.integer :cost, unsigned: true

refrence : http://rubydoc.info/gems/activerecord-mysql-unsigned/0.0.1/frames

answered Nov 23 '13 at 09:02

Mohsen Alizadeh

1,595
12
25

5

Be VERY careful with this gem if you're working within an existing project. This will _override_ Rails' definition of what a primary_key should be to make it unsigned! see here -> https://github.com/waka/activerecord-mysql-unsigned/blob/v0.2.0/lib/activerecord-mysql-unsigned/active_record/v3/connection_adapters/abstract_mysql_adapter.rb#L7-L9 – Mike Lewis Oct 03 '14 at 20:42

unsigned int field in a Ruby on Rails migration?

3 Answers3