描述

Current behavior

When a driver initiates a connection it gets passed the config and uses this straightforward. This creates a problem as soon as commands like db:create and db:drop are about to be executed. Those have no need to be actually be connected to a database directly and this in turn might result in issues while connecting to this database which may not exists already.

Proposed solution

On commands that can omit the database parameter those are going to be stripped away by db-migrate before they actually reach the driver. The drivers in turn have to assure that they handle the default behavior correctly. There are for example open items for postgres https://github.com/db-migrate/pg/issues/5.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

貢獻者指南

技術棧: javascriptnodejssqlpostgresql
領域: database
議題類型: feature
難度: 4
預計時間: 3-5 days
活動狀態: stale
清晰度: clear
前置要求: Node.js experienceDatabase migration conceptsdb migrate driver architecture
新手友善度: 25
研究方向: Investigate the current command execution flow in db migrate, particularly the `db:create` and `db:drop` commands. Identify where the database parameter is passed to drivers. Propose a mechanism to strip the database parameter for these commands before invocation. Also review the open issue in the postgres driver (https://github.com/db migrate/pg/issues/5) to ensure compatibility. Consider adding a flag or method in the driver interface to indicate databaseless support.