Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A <code>OneToOne</code> relationship is unique as it would mean that only one <code>person</code> could be assigned to one <code>location</code> and one <code>location</code> to one <code>person</code>.</p> <p>In your scenario you would want one <code>person</code> to have multiple locations and one <code>location</code> could have multiple <code>person</code>(s). This would be a <code>ManyToMany</code> relationship. </p> <p>In Doctrine when you use a <code>ManyToMany</code> you will specify a <code>JoinTable</code> that Doctrine will manage (You don't have to create an entity for a <code>JoinTable</code>). The <code>JoinTable</code> breaks down the <code>ManyToMany</code> to something like a <code>OneToMany</code> such as one <code>person</code> to many <code>location</code>(s) as shown in example below. The <code>JoinTable</code> will store the values you want when they apply.</p> <pre><code>/** * @ORM\ManyToMany(targetEntity="Location") * @ORM\JoinTable(name="hometown_location", * joinColumns={@ORM\JoinColumn(name="person_id", referencedColumnName="id", unique=true)}, * inverseJoinColumns={@ORM\JoinColumn(name="location_id", referencedColumnName="id")} * ) **/ protected $hometown; /** * @ORM\ManyToMany(targetEntity="Location") * @ORM\JoinTable(name="current_location", * joinColumns={@ORM\JoinColumn(name="person_id", referencedColumnName="id", unique=true)}, * inverseJoinColumns={@ORM\JoinColumn(name="location_id", referencedColumnName="id")} * ) **/ protected $current; public function __construct() { $this-&gt;hometown = new \Doctrine\Common\Collections\ArrayCollection(); $this-&gt;hometown = new \Doctrine\Common\Collections\ArrayCollection(); } </code></pre> <p>If there is no <code>location</code> to assign to <code>hometown</code> or <code>current</code> that is fine, no space is taken up. When you do have a <code>location</code> to assign to either <code>hometown</code> or <code>current</code> it will have to be a valid <code>location</code> from the <code>location</code> table.</p>
    singulars
    1. This table or related slice is empty.
    1. PODoctrine nullable one-to-one relationship still wants to create unique index
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UShcoat
    1. UShcoat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODoctrine nullable one-to-one relationship still wants to create unique index
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COHi @hcoat, thanks for your reply. In my scenario, a person has only one hometown and one current location OR it doesn't have any. So, in my case `Person <--> Location` should be `1 <--> 0..1` for both relations. Because of that I put `OneToOne` relation with `nullable=true`.
      singulars
      1. PO
      1. USMatt
    2. COCurrently, Location table doesn't have any link to any table since the other tables like Person fetch their required information using the `location_id` and I don't want to add more fields to it. While if I use ManyToOne, it needs me to do so :( Is there any way to achieve my goal?
      singulars
      1. PO
      1. USMatt
    3. COAs you may notice, I've implemented this idea without doctrine, and now I am moving to this framework. I think the best database structure for my case is as I mentioned. But if I want to implement it by Doctrine, I need to change that in a kinda inefficient way. before it only needed to join 2 tables and now I have to join 3.
      singulars
      1. PO
      1. USMatt
 

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