-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
doctrine:migration:diff on a postgresql database generate "CREATE SCHEMA public" on the down method #441
Comments
This is an issue with DBAL's Schema API, not the ORM. That's why that issue was closed -- without any feedback on where it was a bug :( Looks like it's still a bug in DBAL (not in migrations itself) doctrine/dbal#1110 |
It is indeed a DBAL issue. Thanks @chrisguitarguy @josensanchez |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not using the public schema, so every table is in others schemas.
i.e:
app.fos_user
data.somtable
gis.postgis_tables
but it doesn't mean that the schema public does not exist. It exist already.
performing the doctrine:migration:diff generate the creation of the public schema
this happens even with the database up to date: It generate an empty up method and only
$this->addSql('CREATE SCHEMA public');
in the down method.
probably it's a doctrine issue and most probably is that it's related to
doctrine/orm#4777
but it's supposed to be solved. Before reopen it I want to be sure that its not related to this project.
I'm using doctrine-migrations 1.1.1 for symfony 3.0
The text was updated successfully, but these errors were encountered: