Closed ananis25 closed 3 weeks ago
Thanks for the PR! Have you confirmed that the migration works on an existing app though? I suspect it won't because the migrations run in the system database but the index is in the app database.
Ah, thats why alembic couldn't generate a migration automatically, I just wrote the migration file by hand. Makes sense that DBOS won't generate migrations in the app database, just make sure the table exists.
This change doesn't really need to affect existing deployments, so we could just leave those? Else we could add a conditional to the DBOS migrate cli I think.
This PR renames the index name for the transactions-output tables in the Application database.
This will also unlock using the same database as app and system database for DBOS, even if ill-advised.