[FLOW3-general] doctrine:migrate error after core migrate to 2.0

Visay Keo keo.visay at typo3.org
Wed Oct 17 11:45:04 CEST 2012


Hi,

i got the following error when I run doctrine:migrate for my package 
that just got migrated to typo3 flow 2.0

---
Uncaught exception in line 633 of 
/var/www/My.Package-Distribution/Packages/Libraries/doctrine/dbal/lib/Doctrine/DBAL/Connection.php: 
SQLSTATE[HY000]: General error: 1005 Can't create
table 'my_db.#sql-53e_191' (errno: 150)

21 PDO::query("ALTER TABLE my_db_domain_model_user ADD CONSTRAINT 
FK_B8FD5F0321E3D446 FOREIGN KEY (flow3_persistence_identifier) 
REFERENCES typo3_party_domain_model_abstractparty
(flow3_persistence_identifier) ON DELETE CASCADE")
20 Doctrine\DBAL\Connection::executeQuery("ALTER TABLE 
my_package_domain_model_user ADD CONSTRAINT FK_B8FD5F0321E3D446 FOREIGN 
KEY (flow3_persistence_identifier) REFERENCES typo3_party
_domain_model_abstractparty (flow3_persistence_identifier) ON DELETE 
CASCADE")
19 Doctrine\DBAL\Migrations\Version::execute("up", FALSE)
18 Doctrine\DBAL\Migrations\Migration::migrate(NULL, FALSE)
17 
TYPO3\Flow\Persistence\Doctrine\Service_Original::executeMigrations(NULL, NULL, 
FALSE, FALSE)
16 
TYPO3\Flow\Command\DoctrineCommandController_Original::migrateCommand(NULL, 
NULL, FALSE, FALSE)
---

doctrine:update seems to be ok without any error. running the 
migrationstatus, i see that the last one from my package is not yet 
migrated but migrate throws me the above error.

If only the base distribution without my package, 
doctrine:update/migrate is always ok.

Anyone has a clue what i should check in my package after i did the 
core:migrate to it? it was working fine in flow3 1.1

thanks,
visay


More information about the FLOW3-general mailing list