Open o5 opened 7 years ago
Using any existing namespace for migration table but NOT public
does work. If you use public.migration
it will fail, when using foobar.migration it will work (if you have that schema in your database)
@mishal: public
IS default schema in Postgres and I think it should work.
Possible workarounds:
A: Use an own PostgreSqlSchemaManager
and override _getPortableTableDefinition
method
B: Create an another schema before running migrations CREATE SCHEMA IF NOT EXISTS ...
I used first and hope the interface will not change :)
Hi there,
I would like to use Doctrine Migrations with PostgreSQL. I want a table
migration_versions
inpublic
schema:I created first migration file and it worked perfectly in first
migrations:migrate
command execution. But second execution of same command fails:I ended in source code of DBAL, and this line causes the problem. If I change
return
statement toproblem is fixed. It's interesting because the change is very old.
Any idea? Is there somebody who uses Doctrine Migrations with PostgreSQL?
Versions:
Thank you.