[Flow] Upgrade from FLOW3 1.1 to Flow 2.0: error with doctrine:migrate
François Suter
fsu-lists at cobweb.ch
Tue Aug 27 20:30:58 CEST 2013
Hi Robert,
> This may be a foreign key constraint issue. This is generally tricky,
> but not impossible to solve - key is to find the right order in which
> you can drop primary keys and constraints so nothing else still depends
> on it.
That was it indeed. I thought I had sorted all those queries in the
right order, but I had got my logic wrong.
> You'll always see that medium-helpful error message with code no. 150.
> Fortunately there's a way to see a bit more: right after the error
> occurred, run a "SHOW ENGINE INNODB STATUS;" query.
Thanks for this tip. That was very useful in getting more details in
order to figure what was wrong.
Cheers
--
Francois Suter
Work: Cobweb Development Sarl - http://www.cobweb.ch
TYPO3: Help the project! - http://typo3.org/contribute/
Appreciate my work? Support me -
http://www.monpetitcoin.com/en/francois/support-me/
More information about the Flow
mailing list