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
When adding a reference to a model, I personally make an initial migration allowing null values for the model_id, fill the ids and only then force the null: false on the id column.
However, this causes a NoMethodError on the display_name of a column. It is absolutely reasonable, but it makes the resource completely unavailable in that intermediate stage.
When adding a reference to a model, I personally make an initial migration allowing null values for the model_id, fill the ids and only then force the
null: false
on the id column.However, this causes a NoMethodError on the display_name of a column. It is absolutely reasonable, but it makes the resource completely unavailable in that intermediate stage.
Perhaps it would make sense to somehow handle this use case?
The text was updated successfully, but these errors were encountered: