yes, it is, and it's weird as well. didn't expect the default to be the problem here. i already tried to fix it but i'm not happy with it:

we have to pass in the `:limit` option for mysql because we want more than 64k. specifically we have to pass in `:limit => 16.megabytes - 1` to let the adapter create the almost correct value of 16777215 (otherwise it will be 2147483647)

since postgres doesn't have any specific limits on text and binary columns, it just ignores the limit parameter in the schema.rb or in any migrations, consequently we can always use `:limit` in the migrations. but, when migrating with mysql, this `:limit` will end up in the schema.rb and when migrating with postgres it won't. so as long as everybody only checks in schema.rbs that got generated by migrations on a mysql database, everything is fine. if somebody migrates with a postgres database, checks that schema.rb in (without the :limits) then somebody on mysql running `rake db:schema:load` will not have the correct limits set.

any ideas besides enforcing all migrations to be done through mysql or messing around with the adapter source code?