Doctrine ORM and External Databases
However, running a package update, or refreshing the database entities results in an exception, claiming a table already exists in the concrete5 database, when it does not, nor should it. It does in fact exist in the external one.
It seems to me that there's an inconsistency here since it's clearly testing the concrete5 database, and then trying to create the database in the external one and throwing an exception citing the concreet5 database.
I don't have any db.xml files, so it must be doctrine code that's doing this. I'd rather it didn't do anything with regard to schema updates etc, so I wonder if anyone knows how to disable that part of the package update and entity refresh?
The error is similar to this:
The table with name 'shiny_new_db.oldtable' already exists.
You might have better luck asking this question in Slack #general.