Allow querying of migration status by user who cannot create a table #3141
aturleyIdeem
started this conversation in
Ideas
Replies: 2 comments 1 reply
|
I'd like to second this concern. In many large organizations, DDL actions (CREATE, DROP, etc.) are restricted to other administrative teams and a separation is enforced. I have no expectations that a GET action (get_pending_migrations()) would have a side-effect of actually trying to CREATE a table. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have a use case where we would like to allow a database user who CANNOT create a table to run
Migrator::get_pending_migrations()to check to see if there are any pending migrations in a MySQL database. But this causesMigrator::install(), which runsCREATE TABLE IF NOT EXISTS seaql_migrations, which fails because the user does not haveCREATE TABLEpermission.I recognize that this might be a bit outside of the standard use case for SeaORM, but it would be nice to be able to use a read-only user for what, on the face of it, would seem to be a read-only operation.
All reactions