Rails Migration: Bigint on PostgreSQL seems to be failing?

ruby-on-rails postgresql activerecord migration bigint
Lonecat picture Lonecat · Aug 15, 2011 · Viewed 13.1k times · Source

Trying to create a table with a bigint column creates a standard integer column instead. What could be going wrong? I don't know where to start looking.

I'm using this in the migration:

create_table :table_name do |t|
  t.integer :really_big_int, limit: 8
end

I'm using Ruby 1.9.2, PostgreSQL 9.0.3 and Rails 3.0.9. I've dropped the database and ran the migrations several times and it still doesn't create the bigint column.

Answer

Chris Barretto picture Chris Barretto · May 23, 2012

For some reason the create table doesn't like bigint. You can, however do it with add_columm using the bigint data type:

add_column :table_name, :really_big_int, :bigint

Then you don't need that limit stuff.

Related questions

Rails migration generates default timestamps (created_at, updated_at) as NULLABLE

Some time ago we upgraded our application to Rails 4 and switched to JRuby. Before that change migrations created the default timestamps as NOT NULL. After that change the NOT NULL is missing. We create these timestamps (created_at, updated_at) …

Read More
Rails 4 LIKE query - ActiveRecord adds quotes

I am trying to do a like query like so def self.search(search, page = 1 ) paginate :per_page => 5, :page => page, :conditions => ["name LIKE '%?%' OR postal_code like '%?%'", search, search], order => 'name' end …

Read More
Find rows with multiple duplicate fields with Active Record, Rails & Postgres

What is the best way to find records with duplicate values across multiple columns using Postgres, and Activerecord? I found this solution here: User.find(:all, :group => [:first, :email], :having => "count(*) > 1" ) But it doesn't seem to work …

Read More