Dealing with that cruft mismatch in schema.rb is a headache — would defiantly speed up developer productivity if we figured out the reasons why different developers’ systems produce slightly different files (this being one of them) and killed those nuances so my schema.rb didn’t change itself even when there are no schema changes.
It is definitely something that does not make me :happy_face: and Matz said Ruby was supposed to make me happy.
Positive over here. People may occasionally have a look at db/schema.rb,
but it's main use case is to automate stuff.
Personally, I wouldn't even make it configurable in this case, we are not
talking about generating a non-readable dump. Some people would even write
it like that if it was their code. A matter of preference, no big deal.