You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when new migrations arrive, they are inserted into database while doing db:migrate. The problem is that description in DB is taken from migration's filename so it's only the labelized version of it (100 chars at max, only A-Z characters).
Proposal:
renaming 'description' to 'label' in database
creating additional 'description' field with full description
It would be best to implement it by creating a new static public variable called $description in each Migration file.
The text was updated successfully, but these errors were encountered:
If this one passes, minion_schema should use utf8 rather than latin1 (right now it doesn't matter anyway because no non-ASCII data is being kept in database)
What is the point of the label in the DB? Identification? It seems to me that this is what the timestamp is for, and the Migration class itself can (as you suggest) provide a proper description. But maybe I'm missing something.
Right now when new migrations arrive, they are inserted into database while doing db:migrate. The problem is that description in DB is taken from migration's filename so it's only the labelized version of it (100 chars at max, only A-Z characters).
Proposal:
It would be best to implement it by creating a new static public variable called $description in each Migration file.
The text was updated successfully, but these errors were encountered: