Can't decide which way to adopt going forward to save people who always execute the same commands on upgrade without checking the notes each time
Can't decide which way to adopt going forward to save people who always execute the same commands on upgrade without checking the notes each time 5 comments
@Gargron Dang. Guess I'll have to read up on how to update to 3.3.0 now. Hopefully I don't screw it up in the process. @Gargron By the way, while upgrading mamot.fr, I wondered if my postgresql schema was up-to-date... I know rails should be doing migration properly, but what if I missed one some day for some obscure uncatched error? (eg I wonder if the "account_id" field is indexed in the "status") @vincib Every db:migrate runs all pending migrations, it’s unlikely you somehow missed some except the most recent ones. If you wanna go the hard way you can db:schema:dump and compare the generated db/schema.rb file using git, but I wouldn’t bother doing it unless you have real reasons to believe something is amiss. |
@Gargron The first one stands out to me more, or could you maybe comine them?