-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
DDC-154: SchemaTool generates cryptic error message in case of typos on referenced column names #2173
Comments
Comment created by giorgiosironi: Transforms the exception in: Sorry for lack of tests but the only ones for SchemaTool needs mysql or other vendor and I cannot run them with sqlite right now. |
Comment created by giorgiosironi: Transform the exception in: Sorry for lack of tests but the SchemaTool ones need mysql or other vendors and I cannot run them right now with sqlite. |
Comment created by @beberlei: Applied and fixed. |
Issue was closed with resolution "Fixed" |
Imported 1 attachments from Jira into https://gist.github.com/bed5ea18c1da9e927fe7 |
Jira issue originally created by user giorgiosironi:
When there is a typo in a @joincolumn(name='...', referencedColumnName='_error_'), the error does not give any clue where to look for:
[09:09:44][giorgio@Indy:/var/www/nakedphp]$ php example/bin/doctrine schema-tool --re-create --config=example/bin/cli-config.php
Doctrine Command Line Interface
Dropping database schema...
Database schema dropped successfully.
Creating database schema...
SchemaTool: exception 'Doctrine\Common\DoctrineException' with message 'Unknown column type' in /var/www/nakedphp/library/Doctrine/Common/DoctrineException.php:111
Stack trace:
#0 [internal function]: Doctrine\Common\DoctrineException::**callStatic('unknownColumnTy...', Array)
#1 /var/www/nakedphp/library/Doctrine/DBAL/Types/Type.php(125): Doctrine\Common\DoctrineException::unknownColumnType(NULL)
#2 /var/www/nakedphp/library/Doctrine/ORM/Tools/SchemaTool.php(329): Doctrine\DBAL\Types\Type::getType(NULL)
The text was updated successfully, but these errors were encountered: