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
I came across an issue when I tried to add an additional column to my child table and realized that the associated view also needed to be updated. As a stop gap, I modified your CreateTheViewForCITIEs method to do a "CREATE OR REPLACE VIEW ...." instead of just a CREATE which allows me to just add the method call in each subsequent migration where I add or remove a column. For the sake of readability by other coders who may not have known what I did, it would be good if you could override the add_column and remove_column methods so that it happens auto-magically. Would be good for ensuring that this key step doesnt get missed
The text was updated successfully, but these errors were encountered:
You are completely right, this point is neither mentionned in the documentation nor "automagically" taken into account. Consequently, I will try as soon as possible to :
mention this point in the documentation,
update the code and either override "add_column" and "remove_column" methods or propose a modification of the CreateTheViewForCITIEs methods just like you have done.
I came across an issue when I tried to add an additional column to my child table and realized that the associated view also needed to be updated. As a stop gap, I modified your CreateTheViewForCITIEs method to do a "CREATE OR REPLACE VIEW ...." instead of just a CREATE which allows me to just add the method call in each subsequent migration where I add or remove a column. For the sake of readability by other coders who may not have known what I did, it would be good if you could override the add_column and remove_column methods so that it happens auto-magically. Would be good for ensuring that this key step doesnt get missed
The text was updated successfully, but these errors were encountered: