db/schema.rb turns mediumtext columns into longtext

[pulver]

In Rails 3.1.1 the following migration line creates a column of MySQL type MEDIUMTEXT:

t.text :example, :limit => 0x555555 # this happens to be the maximum length for MEDIUMTEXT. 0x555556 results in LONGTEXT.

however the resulting line in db/schema.rb is

t.text "example", :limit => 16777215

which creates a column of type LONGTEXT.

I would expect that the database column types created by the migration files would be the same as those created by the db/schema.rb file.

[sikachu]

Hmm .. that decimal representation actually off a lot. I would expect it to be 5592405. Do you mind sending a pull request with a failing test case (and fix?)

[kennyj]

I think that I fixed it.
I'll send pull request.

The below definition is mysql side (strange...) behavior.
text(5592405) => mediumtext
text(5592406) => longtext

Thus, I fixed type_to_sql method to return correct type, when the data type is text with limit.

Please see also http://dev.mysql.com/doc/refman/5.5/en/storage-requirements.html

[kennyj]

I realize mysql side behavior...

If we use latin1 encoding, the limit is 16777215.
But if we use utf-8 encoding, limit is 16777215 / 3 = 5592405

[kennyj]

I'm closing this issue, because the above PR was merged.