feat: support multiple database connections #1879
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1577, closes #1642
Note that this depends on #1838 as it built on top of the refactoring in that branch.
Changes
This PR introduces support for multiple database connections as well as Postgres Schema (sub databases).
Breaking changes
None that should affect the user, but the existing code allowed for parsing multiple schema files for a single connection (i.e., the only connection). However, Laravel saves the schema squash files as
<connection>-schema.sql
. So to able to understand which schema file belongs to what connection I rely on this naming convention to determine the connection name from the filename. In practice this means there should only be one file per connection.For example, the following files would both be parsed under the
mysql
connection:mysql-schema.{sql,dump}
mysql.{sql,dump}