Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-1579

MappedSuperClass and inheritance problem with console generate:entities command

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.1.5
    • Fix Version/s: 2.3
    • Component/s: Tools
    • Security Level: All
    • Labels:
      None
    • Environment:
      Debian 6.0.3 - Linux 2.6.32-5-amd64

      Symfony2 2.0.8 + Doctrine2 2.1.5

      Description

      I have two classes.

      One extends from another. I'm using the annotation @MappedSuperclass
      and operates correctly, but when he did the entities generation
      through the command console, doctrine adds the property and the
      methods of the "father" class in the subclass.

      This is a bug of the command console?

      Really you should not copy them if you do not extend them. When you
      run the update of the database schema, i must delete these fields and
      methods added to obtain the desired result.

      What happens?

      Im usign Symfony 2.

      Thanks!!!!

      Code:

      Father class:

      /********************************************************************

      /**

      • @ORM\MappedSuperclass
        */
        abstract class ConfigBase
        {

      /**

      • @ORM\Column(name="enabled", type="boolean")
        */
        protected $enabled;

      /**

      • Set enabled
        *
      • @param boolean $enabled
        */
        public function setEnabled($enabled) { $this->enabled = $enabled; }

        /**
        * Get enabled
        *
        * @return boolean
        */
        public function getEnabled()
        { return $this->enabled; }

        }

        /********************************************************************

        SubClass

        /********************************************************************

        /**
        * @ORM\Entity
        *
        */
        class UserConfig extends ConfigBase
        {
        /**
        * @var integer $id
        *
        * @ORM\Column(name="id", type="integer")
        * @ORM\Id
        * @ORM\GeneratedValue(strategy="AUTO")
        */
        protected $id;

        /**
        * Get id
        *
        * @return integer
        */
        public function getId()
        { return $this->id; }

        /************************************************/
        /* Auto generated and non desired values */
        /************************************************/
        /**
        * @var boolean $enabled
        */
        private $enabled;

        /**
        * Set enabled
        *
        * @param boolean $enabled
        */
        public function setEnabled($enabled)
        { $this->enabled = $enabled; }

      /**

      • Get enabled
        *
      • @return boolean
        */
        public function getEnabled() { return $this->enabled; }

        Issue Links

          Activity

          Hide
          Lukas Domnick added a comment -

          As of Doctrine 2.3.0, Symfony 2.1.3, this behaviour is still reproducable.
          Mr. Ehlers is correct; generation will work correctly when the super class' properties are set to private scope. However, in that case the Proxy Object's lazy loading can't set the properties in question.

          Show
          Lukas Domnick added a comment - As of Doctrine 2.3.0, Symfony 2.1.3, this behaviour is still reproducable. Mr. Ehlers is correct; generation will work correctly when the super class' properties are set to private scope. However, in that case the Proxy Object's lazy loading can't set the properties in question.
          Hide
          Johan Hendrik Ehlers added a comment -

          I just noticed that this is only an issue if the member has a protected scope in the mapped super class, it works fine for private members.

          Show
          Johan Hendrik Ehlers added a comment - I just noticed that this is only an issue if the member has a protected scope in the mapped super class, it works fine for private members.
          Hide
          Benjamin Eberlei added a comment -

          It is a known problem that will be fixed in 2.3 hopefully.

          Show
          Benjamin Eberlei added a comment - It is a known problem that will be fixed in 2.3 hopefully.

            People

            • Assignee:
              Benjamin Eberlei
              Reporter:
              Sergio Moya
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: