Doctrine DBAL

Handling of explicit Schemas is wrong in comparator

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.2-BETA2
  • Fix Version/s: 2.2
  • Component/s: None
  • Security Level: All
  • 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!

Activity

Hide
Permalink
Benjamin Eberlei added a comment -

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.

Show
Benjamin Eberlei added a comment - 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.

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Benjamin Eberlei
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: