Constraints for OneToMany, ManyToMany etc. Associations
|Priority:||Should have||Due date:|
|Assignee:||Karsten Dambekalns||% Done:||
|Target version:||TYPO3 Flow Base Distribution - 1.0.0|
If Doctrine-Associations are used in FLOW3 which generate Constraints and Foreign keys in the MySql Database, the length of the Constraints and Foreign keys is limited if a database is dumped and loaded again.
So If the object-names become rather long for readability purposes and the Domain-Model has subdomains (<vendor-ns>\Domain\Model\<subdomain>\<object>) the Constraints and Foreign keys generated by the Doctrine ORM/DBAL are rather long. This is no problem as long as the database is not dumped and loaded again.
Updated by Regine Rosewich almost 2 years ago
to be more precise. I mean the names of the Constraints and the Foreign keys (not the data).
Updated by Karsten Dambekalns over 1 year ago
- Status changed from New to Rejected
- Target version set to 1.0.0
Nothing we can do about this. Workaround: dump only the data, create the tables using doctrine:migrate and/or doctrine:update and load the dumped data back in.
The problem here: some of the names are autogenerated by MySQL, and work fine although they are too long to be imported again. After all, exporting them works fine as well. Go figure.