Databases
StackOverflow2013
Postsdbo
POSonata Admin many to many with attributes form
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSonata Admin many to many with attributes form
    primarykey
    data
    text
    <p>I'm using 4 entites :</p> <ol> <li>translator</li> <li>language</li> <li>translator_language</li> <li>site</li> </ol> <p>Translator can have many languages. Languages can have many translators. A site can be assigned a couple translator/language.</p> <p>So I have been forced to create translator_language even if there is no "real attribute" inside.</p> <pre><code>class Language { /** * @var \XX\TranslateBundle\Entity\TranslatorLanguage * * @ORM\OneToMany(targetEntity="TranslatorLanguage", mappedBy="language") */ private $translators; </code></pre> <p>xx</p> <pre><code>class Translator { /** * @var XX\TranslateBundle\Entity\TranslatorLanguage * * @ORM\OneToMany(targetEntity="TranslatorLanguage", mappedBy="translator") */ private $languages; </code></pre> <p>xx</p> <pre><code>class TranslatorLanguage { /** * @var XX\TranslateBundle\Entity\Translator * * @ORM\Id * @ORM\ManyToOne(targetEntity="Translator", inversedBy="languages") * @ORM\JoinColumn(name="translatorID", referencedColumnName="ID", nullable=false) */ private $translator; /** * @var XX\TranslateBundle\Entity\Language * * @ORM\Id * @ORM\ManyToOne(targetEntity="Language", inversedBy="translators") * @ORM\JoinColumn(name="languageID", referencedColumnName="ID", nullable=false) */ private $language; /** * @var XX\TranslateBundle\Entity\TranslatorSite * * @ORM\OneToMany(targetEntity="TranslatorSite", mappedBy="translatorLanguage") */ private $translatorSites; </code></pre> <p>Mapping is ok ([Mapping] OK - The mapping files are correct.)</p> <p>With ManyToMany mapping, I could do </p> <pre><code>$formMapper-&gt;add('languages', null, array('required' =&gt; false, 'expanded' =&gt; true)) </code></pre> <p>in TranslatorAdmin.php, and that would render checkboxes for each languages, and checked one for languages associated to translator, now I'm trying to get that with my new architecture, but no way I manage to do that easily.</p> <p>I don't really want to create a translatorlanguageAdmin because I don't want the form to be the same, coming from translator or language (as it can be done with simple many to many mapping)</p> <p>Do I need to associate a query and a template to the showMapper ? Or am I missing something easy?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScopndz
    1. UScopndz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COgeneral question: why dont you create a many-to-many relationship between language and translator and add the sites to your translator?
      singulars
      1. POSonata Admin many to many with attributes form
      1. USnifr
    2. COBecause that wouldn't mean the same thing I guess, I want to associate associations of translator/language to a site, not a translator with all his languages.
      singulars
      1. POSonata Admin many to many with attributes form
      1. UScopndz
    3. COthen you should create many-to-many between translator -> language and side and translator -> language. a translator can have languages he is able or allowed to translate, a site can have different languages and different translators .. there is no need for the fourth entity translatorSite, just makes things more complicated :)
      singulars
      1. POSonata Admin many to many with attributes form
      1. USnifr
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload