Thoughts on not quoting the default migration option when its a supported db function?

I recently created this PR but it seems that the solution was deemed too specific to mysql and also overloading the default option wasn’t what was desired. The need is there however, and I’d like to hear what everyone thinks on a path forward.

A simple example is when the DEFAULT is a CURRENT_TIMESTAMP.


–John Negron

I think this is fine, but the TL;DR of my thoughts is that it should be through a default_function key, not a default key. I haven’t looked closely enough at the issue to see how much that would impact the rest of AR outside of the schema dumper/definitions API