It is an limitation of the implementation. All database adapters share the same migrations helpers. If the SQLite3 adapter doesn't not accept the `limit` option to a string column and we raise an error when the users pass it the PostgreSQL adapter will also raise an error even that it is supported for that database.
Today it is also possible to write plugins to the migration helper easily without having to monkey patch them, changing to raise errors when the option is unknown will require these plugins to monkey patch them. On Mon, Jun 13, 2016 at 1:19 PM Ian Ker-Seymer <i.kersey...@gmail.com> wrote: > Rafael, why would it not be possible? Is this an architectural issue with > the current rails code? > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at https://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
