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
It would be good to be able to have migrations run from extensions, so that they don't have to:
a. Have a separate paster command to create the database tables they need
b. Have workarounds when the db schema changes
c. Try and autoload tables at startup time.
Integrating with db upgrade appears to be the favoured approach.
The text was updated successfully, but these errors were encountered:
We decided to close old issues that are not actively worked on so that we can focus our effort and attention on issues affecting the current versions of CKAN.
If this issue is still affecting the version of CKAN you're working with now, please feel free to comment or reopen the issue.
If you do reopen this issue, please update it with new details. One reason it might not have been resolved in the past is that it wasn't clear how a contributor could address the issue.
It would be good to be able to have migrations run from extensions, so that they don't have to:
a. Have a separate paster command to create the database tables they need
b. Have workarounds when the db schema changes
c. Try and autoload tables at startup time.
Integrating with
db upgrade
appears to be the favoured approach.The text was updated successfully, but these errors were encountered: