Open pdelboca opened 4 days ago
@tino097 @jqnatividad I'm wondering if this is something you would like to handle in a database migration (like you have for checking aps_jobs_id
and logs.id
) or if this should be handled by a migration on the project dealing with this.
Describe the bug Database migration runs successfully but they do not create the required columns. Running
datapusher-plus
will raise an error:column "job_key" of relation "jobs" does not exist
To Reproduce Steps to reproduce the behavior:
ckanext-xloader
runningckanext-xloader
datapusher-plus
datapusher-plus
database migrations (ckan datapusher init-db
andckan db upgrade -p datapusher_plus
)Expected behavior Running database migrations will successfully create the database tables or raise an error if conflicting tables already exist. (Maybe this is a error in CKAN)
Additional context So I have an instance with
ckanext-xloader
running and I'm migrating todatapusher-plus
. Deactivatingckanext-xloader
left thejobs
table in the database. This is causing some inconsistent behaviour in CKAN since when I'm executingckan datapusher init-db
I have a Success confirmation message but the table is not created. I only have a leftover of the jobs table thatckanext-xloader
created.As I mention, this is probably an error in CKAN, but I wanted to create an issue here since it may happen to other users trying to migrate to
datapusher-plus
.