a2lix TranslationFormBundle AND Gedmo Doctrine Extension Translatable with just one Translation table

问题

I am trying to use the a2lix TranslationFormBundle ( https://github.com/a2lix/TranslationFormBundle ) with a Symfony2 project. I have been looking at docs and specifically at this demo: https://github.com/a2lix/Demo/tree/master/src/A2lix/DemoTranslationBundle

I noticed all examples in both the doc and the demo use specific translation tables (end entity) for each translatable entity, as set in the class annotation with

@Gedmo\TranslationEntity(class="A2lix\DemoTranslationBundle\Entity\ProductGedmoTranslation")

My idea was to stay with just one table, like the ext_translations table that the Gedmo Doctrine Extension Translatable creates and manages.

Is this possible or does the TranslationFormBundle absolutely need separate tables? Does anyone have a working example?

TIA

回答1:

With the current implementation of TranslationFormBundle, you need separate tables. Use an only one ext_translations table is not plan.

来源：https://stackoverflow.com/questions/22408833/a2lix-translationformbundle-and-gedmo-doctrine-extension-translatable-with-just