Postgres Array of Integers changes to simply Integer in production

[lmcardle]

Previously I was running this app in Rails --pre and all worked well. However, I recently switched to RC1 and that's when I started getting this issue.

In development, using Postgres as the database, I am creating a column that will store an array of integers. If I look at the schema.rb file, everything looks right and actually runs correctly in the console. Below is my schema.rb file for that table.

create_table "cards", force: true do |t|
t.string "miscellaneous", default: [], array: true
t.integer "ministries", default: [], array: true
end

When I deploy to production, all arrays that are of "string" type still work as expected. However, the "integer" type arrays are being changed from type array to simply type integer. See below for the schema.rb file:

create_table "cards", force: true do |t|
t.string "miscellaneous", default: "{}"
t.integer "ministries", default: 0
end

Any idea what might have caused this? As I said, it was working in production fine with the pre version of Rails 4. This just started when I upgraded to RC1.

[lmcardle]

Might be the same as #10432.

[lmcardle]

Note, this may also be happening in development, I just haven't started the app all over again in development. I blew away the server and set up a new one in production, which is why I am now only seeing the issue in production.

[scudco]

The problem noted in #10432 was cropping up in migrations using the add_column method. What do your migrations look like? Is it possible your miscellaneous column is being created within a create_table while your ministries column in being added with add_column? If so, this is likely the same issue described #10432

[lmcardle]

They were all added via add_column, both the "string" and "integer" type array:

add_column :cards, :miscellaneous, :string, array: true, default: '{}'
add_column :cards, :ministries, :integer, array: true, default: '{}'

The string type array does get set properly, just not the integer.

[scudco]

Oh, I just now noticed that they're both missing the array key in your db/schema.rb. This is the same bug as #10432 then.