+1
I had this idea too. It's annoying when looking at diff when something changes
and it's not obvious.
If someone wants to take a stab at it, please feel free.
-Prem
> On Jul 5, 2016, at 8:08 AM, Xavier Noria wrote:
>
> Positive over here. People may occasionally have a look at db/schema.
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 co
Yes please :+1:
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 did
schema.rb git diff are often harder to read as adding a column or argument
could add/remove whitespace for other columns definitions.
Let's say I have a `users` table with a `first_name` column:
create_table "users", force: :cascade do |t|
t.string "first_name", null: false
end
If I add anot
