Doctrine DBAL
  1. Doctrine DBAL
  2. DBAL-75

SchemaTool->getDropSchemaSql ignores schema name

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0-RC4
    • Fix Version/s: 2.0-RC5
    • Component/s: Schema Managers
    • Labels:
      None
    • Environment:
      NA

      Description

      When including the schema name as part of the table name, i.e.

      /**
       * @Entity
       * @Table(name="ayso.players")
       */
      class PlayerItem
      

      SchemaTool->getDropSchemaSql returns "DROP TABLE players" instead of "DROP TABLE ayso.players"

      Furthermore, SchemaTool->getUpdateSchemaSql() always returns CREATE TABLE ayso.players followed by DROP TABLE players. It thinks there are two different tables.

      Also, the online document still indicates that @Table accepts 'schema' as an attribute.

        Activity

        Art Hundiak created issue -
        Art Hundiak made changes -
        Field Original Value New Value
        Description When including the schema name as part of the table name, i.e.
        {code}
        /**
         * @Entity
         * @Table(name="ayso.players")
         */
        class PlayerItem
        {code}

        SchemaTool->getDropSchemaSql returns "DROP TABLE players" instead of "DROP TABLE ayso.players"

        Furthermore, SchemaTool->getUpdateSchemaSql() always returns CREATE TABLE ayso.players followed by DROP TABLE players. It think there are two different tables.

        Also, the online document still indicates that @Table accepts 'schema' as an attribute.
        When including the schema name as part of the table name, i.e.
        {code}
        /**
         * @Entity
         * @Table(name="ayso.players")
         */
        class PlayerItem
        {code}

        SchemaTool->getDropSchemaSql returns "DROP TABLE players" instead of "DROP TABLE ayso.players"

        Furthermore, SchemaTool->getUpdateSchemaSql() always returns CREATE TABLE ayso.players followed by DROP TABLE players. It thinks there are two different tables.

        Also, the online document still indicates that @Table accepts 'schema' as an attribute.
        Benjamin Eberlei made changes -
        Project Doctrine 2 - ORM [ 10032 ] Doctrine DBAL [ 10040 ]
        Key DDC-889 DBAL-75
        Affects Version/s 2.0-RC4 [ 10111 ]
        Affects Version/s 2.0-BETA4 [ 10072 ]
        Component/s Schema Managers [ 10057 ]
        Component/s ORM [ 10012 ]
        Benjamin Eberlei made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Roman S. Borschel [ romanb ] Benjamin Eberlei [ beberlei ]
        Fix Version/s 2.0-RC5 [ 10113 ]
        Resolution Fixed [ 1 ]
        Benjamin Eberlei made changes -
        Workflow jira [ 12143 ] jira-feedback2 [ 17677 ]
        Benjamin Eberlei made changes -
        Workflow jira-feedback2 [ 17677 ] jira-feedback3 [ 20032 ]

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Art Hundiak
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: