Schema dump produces invalid ruby code with CURRENT_TIMESTAMP column default

[phillipp]

When you dump a MySQL tablewith schema_plus where a column has "CURRENT_TUIMESTAMP" as the default value, the schema dump contains invalid ruby code:

t.datetime "created",           :default=>#<Proc:0x000055a1df04d748@(eval):1 (lambda)>, :null=>false

This is because the schema dump "converter" in schema_plus/core/active_record/schema_dumper.rb uses eval to make the m[:options]a hash, but that contains a lambda:

SchemaDump::Table::Column.new name: m[:name], type: m[:type], options: eval("{" + m[:options] + "}"), comments: []

Where m[:options] is a string: default: -> { "CURRENT_TIMESTAMP" }, null: false.

I'm not sure what possible solutions look like. Maybe saving the original string and use it for the dump, but use the parsed one for all other purposes? Do you have any ideas?

[atomical]

I've run into this too. I've got a working solution but now I have an index issue to fix with as well.

master...atomical:schema_plus_core:support_for_default_procs