Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PSQL - Issue with Phinx if migration_table is not in the public schema #2315

Closed
JulienChavee opened this issue Oct 2, 2024 · 1 comment · Fixed by #2316
Closed

PSQL - Issue with Phinx if migration_table is not in the public schema #2315

JulienChavee opened this issue Oct 2, 2024 · 1 comment · Fixed by #2316
Labels

Comments

@JulienChavee
Copy link
Contributor

Hello,

Since #2309 there is an issue with Phinx if the migration_table is not in the default public schema.
Currently we specify the schema in the configuration, but as the class variable in the PostgresAdapter is assigned after the parent::setOptions($options), and as the verification if the table exists is done in this function as well, when it resolves the schema name it uses the default one, instead of taking the one from the configuration.

@MasterOdin
Copy link
Member

Thanks for the bug report! This has been fixed in the newly released 0.16.5.

@MasterOdin MasterOdin added the bug label Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants