rmw / enum_ref_table Goto Github PK

There are some outstanding improvements/issues that are open on enum_table, and there has now been an improvement made and an issue opened on this repo. If this was to be a fork of enum_table, it'd make sharing changes and improvements between the projects much easier.

The README to this project states that there are name conflicts with the enum_column3 gem. I'm wondering if this could be solved by instead renaming something within enum_table itself, writing some sort of monkey patch to achieve the desired behavior, or if whatever is conflicting can be renamed in a branch called no_conflict or something that a project's Gemfile could be pointed to.

I just think having multiple apps in production with different developers working on them can help smooth out rough edges and reveal edge cases sooner, which could benefit all users of the gem.

Let me know thoughts @rmw @oggy

In schema.rb, this gem places the table creation UNDER the all of the foreign key constraints. This is a problem because the constraint can't be created due to this ordering (in schema:load & test:prepare)

Noticed that the foreigner was potentially part to blame for the ordering issue...but we know you and we're harassing you about it 😄

For example:

# table
  create_table "media", :force => true do |t|
    t.integer  "user_id",                  :null => false
    t.integer  "couple_id",                :null => false
    t.string   "uri",                      :null => false
    t.integer  "type_id",                  :null => false
    t.string   "mime_type",  :limit => 64, :null => false
    t.datetime "created_at",               :null => false
    t.datetime "updated_at",               :null => false
  end

# stuff
  add_foreign_key "media", "media_types", :name => "media_type_id_fk", :column => "type_id"
# stuff

  create_enum_ref_table "media_types", force: true do |t|
    t.add "image", 1
  end

end