[DBAL-204] Handling of explicit Schemas is wrong in comparator Created: 18/Jan/12 Updated: 21/Jan/12 Resolved: 21/Jan/12
|Reporter:||Benjamin Eberlei||Assignee:||Benjamin Eberlei|
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!
|Comment by Benjamin Eberlei [ 21/Jan/12 ]|
This includes facilities to filter schema assets when creating from a SchemaManager:
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.