[DBAL-75] SchemaTool->getDropSchemaSql ignores schema name Created: 23/Nov/10  Updated: 12/Dec/10  Resolved: 12/Dec/10

Status: Resolved
Project: Doctrine DBAL
Component/s: Schema Managers
Affects Version/s: 2.0-RC4
Fix Version/s: 2.0-RC5

Type: Bug Priority: Minor
Reporter: Art Hundiak Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 0
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.



 Comments   
Comment by Benjamin Eberlei [ 12/Dec/10 ]

Moved to DBAL, its a DBAL issue.

Comment by Benjamin Eberlei [ 12/Dec/10 ]

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

Generated at Wed Aug 20 05:08:14 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.