Skip to content

Loading…

DBAL-570: [GH-349] Existing columns not found (at least in mysql) #1781

Closed
doctrinebot opened this Issue · 3 comments

2 participants

@doctrinebot

Jira issue originally created by user @doctrinebot:

This issue is created automatically through a Github pull request on behalf of lucasvanlierop:

Url: #349

Message:

Existing columns in the database were not found since database name was being used instead of just the db name part of the dsn.
Two examples where I ran into this

  • Schema tool trying to create existing columns over and over again.
  • Migrations not being able to set a primary key for columns created earlier.

Note that this fix is quite basic it might the case the conversion has to happen earlier on in the code for example by adding a 'getDatabaseName()' method to \Doctrine\DBAL\Connection or maybe just apply it in \Doctrine\DBAL\Platforms\MySqlPlatform::getListTableIndexesSQL()?

Please let me know

@doctrinebot

Comment created by @doctrinebot:

A related Github Pull-Request [GH-349] was closed:
#349

@doctrinebot

Comment created by @beberlei:

PR was closed

@doctrinebot

Issue was closed with resolution "Invalid"

@doctrinebot doctrinebot added the Bug label
@beberlei beberlei was assigned by doctrinebot
@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.