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
To be compatible with diesel print-schema command, I would suggest we can rename the migration table to something else which starts with __ (a double underscore).
The text was updated successfully, but these errors were encountered:
hum, what is the advantage with this? Don't diesel and refinery kinda overlap? My issue with this is the same with changing the type on the version column: a breaking change that envolves manually renaming a table. For this I would prefer we actually go for #109 with the default being refinery_schema_history
To be compatible with diesel print-schema command, I would suggest we can rename the migration table to something else which starts with __ (a double underscore).
The text was updated successfully, but these errors were encountered: