`sea-orm-migration` CLI shouldn't always connect to a database
fee1-dead opened this issue · 0 comments
fee1-dead commented
Description
When using the migration CLI to generate a new migration, it fails because I haven't setup the SSH tunnel to the database configured. This shouldn't happen since generating new migrations should not require a database connection.
Steps to Reproduce
- Run the migration CLI to generate a new migration e.g.
cargo run -p migration -- generate "update table"
Expected Behavior
migration gets generated successfully
Actual Behavior
fails with some error like Fail to acquire database connection: Conn(SqlxError(PoolTimedOut))
Reproduces How Often
always
Workarounds
just setup the ssh tunnel to the database