Skip to content

Instantly share code, notes, and snippets.

@mrimann
Created November 30, 2012 12:16
Show Gist options
  • Save mrimann/4175455 to your computer and use it in GitHub Desktop.
Save mrimann/4175455 to your computer and use it in GitHub Desktop.
use TYPO3\Flow\Annotations as Flow;
use Doctrine\ORM\Mapping as ORM;
/**
* A User
*
* @Flow\Entity
*/
class User {
/**
* @var \TYPO3\Flow\Security\Account
* @ORM\ManyToOne
*/
protected $account;
@mrimann
Copy link
Author

mrimann commented Nov 30, 2012

If someone stumbles upon this issue: It could be solved by deleting the table and re-creating it with utf-8 definition - then a doctrin:update ran through without any further problem.

See: https://twitter.com/brgmn/status/274243407197655040

@kdambekalns
Copy link

Since 2.3 Doctrine adds charset/collation information, overriding the default from the DB that was used before. If those do not match, it breaks. Recommended way around this: use migrations, rather than update and make sure the charset data matches (or remove it to use the DB default).

@kdambekalns
Copy link

Oh, and always remember: SHOW ENGINE INNODB STATUS is your best friend when you hit error 150…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment