You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I built out migration snapshots for all of our plugins for an application were building a few weeks ago no problem. Recently we refactored one of them so much that I'm trying to build a new initial migration for it based on a snapshot.
The following command is no longer working. Example uses a plugin called 'Inventory' with connection 'inventory':
# running this from parent application
bin/cake bake migration_snapshot TestingMigration -p Inventory -c inventory
I get the following:
[InvalidArgumentException]
There was a problem connecting to the database: SQLSTATE[28000] [1045] Access denied for user 'my_ap
p'@'localhost' (using password: YES)
So it's attempting to use the default connection. The connection I'm trying to use does however exist, so it shouldn't be falling back.
I also noticed that it is able to connect, by enabling the mysql general_log I can see:
150528 14:26:24 526861 Connect root@localhost on inventory
526861 Query SET time_zone = '+0:00'
526861 Query SET NAMES utf8
526861 Query SHOW TABLES FROM `inventory`
526862 Connect my_app@localhost on my_app
526862 Connect Access denied for user 'my_app'@'localhost' (using password: YES)
526861 Quit
So it seems that it's able to use the specified connection to run SHOW TABLES, but then it immediately goes back to the default connection after that and fails.
Am I doing something wrong here or has a bug been introduced recently?
The text was updated successfully, but these errors were encountered:
I checked it out and it seems to be something I introduced when implementing the mark_migrated feature (meaning that baked snapshot will be automatically mark as migrated).
I'll try to fix this.
I built out migration snapshots for all of our plugins for an application were building a few weeks ago no problem. Recently we refactored one of them so much that I'm trying to build a new initial migration for it based on a snapshot.
The following command is no longer working. Example uses a plugin called 'Inventory' with connection 'inventory':
I get the following:
So it's attempting to use the default connection. The connection I'm trying to use does however exist, so it shouldn't be falling back.
I also noticed that it is able to connect, by enabling the mysql
general_log
I can see:So it seems that it's able to use the specified connection to run
SHOW TABLES
, but then it immediately goes back to the default connection after that and fails.Am I doing something wrong here or has a bug been introduced recently?
The text was updated successfully, but these errors were encountered: