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
migrations:migrate --write-sql ~/migration.sql
In ConnectionError.php line 19:
REFERENCES command denied to user 'xxxuser'@'x.x.x.x' for table 'xx_table';
This user does not have full database permissions for most of it - can not create tables, can not alter tables etc..
Previously with doctrine/migrations v 1.x was not executing migrations inside database and no need for user to have all permissions.
We need this functionality because during release we are passing migration.sql file to hosting to review it and execute it on production server.
We do not want to have this web server user all permissions on database to be able to generate migration script.
As a work around we found that running with dry-run we can almost achieve it. migrations:migrate --dry-run --write-sql ~/migration.sql
but we need to go into migration.sql file and add insert versions into migrations table.
INSERT INTO doctrine_migration_versions (version) VALUES ('Migrations\Version2021xxxxxxxx');
The text was updated successfully, but these errors were encountered:
Version - "doctrine/migrations": "^3.2",
migrations:migrate --write-sql ~/migration.sql
In ConnectionError.php line 19:
REFERENCES command denied to user 'xxxuser'@'x.x.x.x' for table 'xx_table';
This user does not have full database permissions for most of it - can not create tables, can not alter tables etc..
Previously with doctrine/migrations v 1.x was not executing migrations inside database and no need for user to have all permissions.
We need this functionality because during release we are passing migration.sql file to hosting to review it and execute it on production server.
We do not want to have this web server user all permissions on database to be able to generate migration script.
As a work around we found that running with dry-run we can almost achieve it.
migrations:migrate --dry-run --write-sql ~/migration.sql
but we need to go into migration.sql file and add insert versions into migrations table.
INSERT INTO doctrine_migration_versions (version) VALUES ('Migrations\Version2021xxxxxxxx');
The text was updated successfully, but these errors were encountered: