Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Extending an entity is the way to go. In the Doctrine2 world, they talk about inheritance mapping. Here a code example. It defines a <code>BaseEntity</code> then it is extendsed to create a <code>BaseAuditableEntity</code> and finally there is a <code>User</code> entity extending <code>BaseAuditableEntity</code>. The trick is to use the <code>@Orm\MappedSuperclass</code> annotation. This inheritance scheme will create a single table even if there is three entities in my relationships graph. This will then merge all properties into a single table. The table created will contains every property mapped through the relations, i.e. properties from BaseAuditableEntity and from User. Here the code examples:</p> <p><code>Acme\WebsiteBundle\Entity\BaseEntity.php</code></p> <pre><code>namespace Acme\WebsiteBundle\Entity; use Doctrine\ORM\Mapping as Orm; /** * @Orm\MappedSuperclass */ class BaseEntity { } </code></pre> <p><code>Acme\WebsiteBundle\Entity\BaseAuditableEntity.php</code></p> <pre><code>namespace Acme\WebsiteBundle\Entity; use Doctrine\ORM\Mapping as Orm; /** * @Orm\MappedSuperclass */ class BaseAuditableEntity extends BaseEntity { private $createdBy; /** * @Orm\Column(type="datetime", name="created_at") */ private $createdAt; /** * @Orm\ManyToOne(targetEntity="User") * @Orm\JoinColumn(name="updated_by", referencedColumnName="id") */ private $updatedBy; /** * @Orm\Column(type="datetime", name="updated_at") */ private $updatedAt; // Setters and getters here } </code></pre> <p><code>Acme\WebsiteBundle\Entity\User.php</code></p> <pre><code>namespace Acme\WebsiteBundle\Entity; use Acme\WebsiteBundle\Entity\BaseAuditableEntity; use Doctrine\ORM\Mapping as Orm; /** * @Orm\Entity(repositoryClass="Acme\WebsiteBundle\Entity\Repository\UserRepository") * @Orm\Table(name="acme_user") */ class User extends BaseAuditableEntity implements AdvancedUserInterface, \Serializable { /** * @Orm\Id * @Orm\Column(type="integer") * @Orm\GeneratedValue */ private $id; /** * @Orm\Column(type="string", name="first_name") */ private $firstName; /** * @Orm\Column(type="string", name="last_name") */ private $lastName; /** * @Orm\Column(type="string", unique="true") */ private $email; // Other properties // Constructor // Setters and getters } </code></pre> <p>Here a link to the official inheritance mapping documentation of Doctrine 2.1: <a href="http://www.doctrine-project.org/docs/orm/2.1/en/reference/inheritance-mapping.html" rel="noreferrer">here</a></p> <p>Hope this helps, don't hesitate to comment if you need more information.</p> <p>Regards,<br/> Matt</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you extend an entity in Symfony2 like you used to be able to in Symfony 1?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMatt
    1. USMatt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do you extend an entity in Symfony2 like you used to be able to in Symfony 1?
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThat is brilliant. I knew it must have been possible. Thanks Matt.
      singulars
      1. PO
      1. USAdam Stacey
    2. COAssume, I have `BaseAuditableEntity.php` have column `lastName` with nullable =false, then on extending the class to `User.php`. I need to change the above coulumn lastname accept null values(nullable=true). Will you please help me, how to do so?
      singulars
      1. PO
      1. USJustin John
    3. COIn your `User.php` class, try to redfine the `lastName` property and the annotation associated to it. Maybe this will override what was previously set in the base entity. If it doesn't work, I fear I cannot help further. Try to ask on the doctrine2 mailing list. If you find a solution, don't hesitate to report it here.
      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