Bug #44821

Migration file is not able to apply with current Doctrine

Added by Adrian Föder over 2 years ago. Updated over 2 years ago.

Status:Closed Start date:2013-01-26
Priority:Must have Due date:
Assigned To:- % Done:

0%

Category:-
Target version:-

Description

When attempting to execute the MySQL migration file ...40946, introduced in I782ae08c80ebd65214baac2e163729ef442023c6 (https://review.typo3.org/#/c/15515/), the following occurs:

$ ./flow doctrine:migrationexecute 20121011140946
Uncaught Exception
  Unknown database type bit requested,
  Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

More Information
  Exception code      #0
  File                ...\Packages\Libraries\doctrine\dbal\lib\Doctrine\DBAL\Platforms\AbstractPlatform.php line 321

Probably that's of a new Doctrine "feature"?


Addition: ok, obviously the error message should be rather >>Unkown database type "bit" requested<<; this is the exception trail:

Uncaught exception in line 112 of ...\Packages\Libraries\doctrine\dbal\lib\Doctrine\DBAL\Schema\MySqlSchemaManager.php: Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

25 Doctrine\DBAL\Platforms\AbstractPlatform::getDoctrineTypeMapping("bit")
24 Doctrine\DBAL\Schema\MySqlSchemaManager::_getPortableTableColumnDefinition(array|9|)
23 Doctrine\DBAL\Schema\AbstractSchemaManager::_getPortableTableColumnList("bittest", "phx-edsh", array|1|)
22 Doctrine\DBAL\Schema\AbstractSchemaManager::listTableColumns("bittest")
21 Doctrine\DBAL\Schema\AbstractSchemaManager::listTableDetails("bittest")
20 Doctrine\DBAL\Schema\AbstractSchemaManager::listTables()
19 Doctrine\DBAL\Schema\AbstractSchemaManager::createSchema()
18 Doctrine\DBAL\Migrations\Version::execute("up", FALSE)
17 TYPO3\Flow\Persistence\Doctrine\Service_Original::executeMigration("20121011140946", "up", NULL, FALSE)
16 TYPO3\Flow\Command\DoctrineCommandController_Original::migrationExecuteCommand("20121011140946", "up", NULL, FALSE)
15 call_user_func_array(array|2|, array|4|)
14 TYPO3\Flow\Cli\CommandController_Original::callCommandMethod()
13 TYPO3\Flow\Cli\CommandController_Original::processRequest(TYPO3\Flow\Cli\Request, TYPO3\Flow\Cli\Response)
12 TYPO3\Flow\Mvc\Dispatcher_Original::dispatch(TYPO3\Flow\Cli\Request, TYPO3\Flow\Cli\Response)
11 TYPO3\Flow\Mvc\Dispatcher::dispatch(TYPO3\Flow\Cli\Request, TYPO3\Flow\Cli\Response)
10 call_user_func_array(array|2|, array|2|)
9 TYPO3\Flow\Mvc\Dispatcher::Flow_Aop_Proxy_invokeJoinPoint(TYPO3\Flow\Aop\JoinPoint)
8 TYPO3\Flow\Aop\Advice\AdviceChain::proceed(TYPO3\Flow\Aop\JoinPoint)
7 TYPO3\Flow\Security\Aspect\RequestDispatchingAspect_Original::blockIllegalRequestsAndForwardToAuthenticationEntryPoints(TYPO3\Flow\Aop\JoinPoint)
6 TYPO3\Flow\Aop\Advice\AroundAdvice::invoke(TYPO3\Flow\Aop\JoinPoint)
5 TYPO3\Flow\Aop\Advice\AdviceChain::proceed(TYPO3\Flow\Aop\JoinPoint)
4 TYPO3\Flow\Mvc\Dispatcher::dispatch(TYPO3\Flow\Cli\Request, TYPO3\Flow\Cli\Response)
3 TYPO3\Flow\Cli\CommandRequestHandler::handleRequest()
2 TYPO3\Flow\Core\Bootstrap::run()
1 require("...\Packages\Framework\TYPO3.Flow\Scripts\flow.php")
/pre>

History

#1 Updated by Adrian Föder over 2 years ago

  • Status changed from New to Closed

aye we should add a "shame corner"... I had a table with this name, for some temporary testing purposes obviously...

Also available in: Atom PDF