1. `add_column` is a lower level building block than `t.column`. The higher level methods are composed of these lower level building blocks. That's why you get more combined behavior when using higher level constructs.
2. There is an open PR about PostgreSQL opclass support. See https://github.com/rails/rails/pull/19090 Cheers, -- Yves On Monday, August 31, 2015 at 6:00:26 AM UTC+2, 郑伟 wrote: > > > 1. Why add_column not support index: true ？ > 2. Any plan to support postgres jsonb_path_ops GIN index with > somethings like index: {using: "gin_path"}? it seem like more fast > than gin, and less diskspace usage. I had to use like this in migrate > > ``` > > CREATE INDEX index_notifications_on_data ON notifications USING gin (data > jsonb_path_ops); > ``` > > But schema.rb is not worked, it only generate default gin index jsonb_ops > instead of jsonb_path_ops. > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
