[DBAL-204] Handling of explicit Schemas is wrong in comparator Created: 18/Jan/12  Updated: 21/Jan/12  Resolved: 21/Jan/12

Status: Resolved
Project: Doctrine DBAL
Component/s: None
Affects Version/s: 2.2-BETA2
Fix Version/s: 2.2
Security Level: All

Type: Bug Priority: Major
Reporter: Benjamin Eberlei Assignee: Benjamin Eberlei
Resolution: Fixed Votes: 0
Labels: None


 Description   

if you are on db "foo" and compare table "bar" to "foo.bar". it shouldnt drop one and create the other one. They are the same!



 Comments   
Comment by Benjamin Eberlei [ 21/Jan/12 ]

Fixed.

This includes facilities to filter schema assets when creating from a SchemaManager:

$connection->getConfiguration()->setFilterSchemaAssetsExpression("foo\.bar");

Additionally in the ORM now when using a database vendor that does not support schemas the "namespaced" assets are removed.

Say you are connected to database "foo" and you have an entity defined as @Table("bar.baz"), then all SQL generated for that entity will be removed.

Generated at Fri Oct 31 18:45:34 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.