Skip to content

Loading…

DBAL-204: Handling of explicit Schemas is wrong in comparator #1377

Closed
doctrinebot opened this Issue · 2 comments

2 participants

@doctrinebot

Jira issue originally created by user @beberlei:

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!

@doctrinebot

Comment created by @beberlei:

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.

@doctrinebot

Issue was closed with resolution "Fixed"

@doctrinebot doctrinebot added the Bug label
@beberlei beberlei was assigned by doctrinebot
@doctrinebot doctrinebot added this to the 2.2 milestone
@doctrinebot doctrinebot closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.