DBAL-75: SchemaTool->getDropSchemaSql ignores schema name #1977

Closed
doctrinebot opened this Issue Nov 23, 2010 · 3 comments

2 participants

@doctrinebot

Jira issue originally created by user cerad:

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.

@doctrinebot

Comment created by @beberlei:

Moved to DBAL, its a DBAL issue.

@doctrinebot

Comment created by @beberlei:

Fixed in DBAL master, will be included for RC5. Then linked against ORM RC2

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot doctrinebot added the Bug label Dec 7, 2015
@beberlei beberlei was assigned by doctrinebot Dec 7, 2015
@doctrinebot doctrinebot added this to the 2.0-RC5 milestone Dec 7, 2015
@doctrinebot doctrinebot closed this Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment