mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
PHP7 on AWS Deployment: MappingException "Duplicate definition of column" #5338
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @spointecker on GitHub (Dec 5, 2016).
Originally assigned to: @Ocramius on GitHub.
Hello,
I am currently facing an error for a week now and I have no clue what is happening here.
We run this command on deploy:
php bin/console cache:clear --env=prod && php bin/console cache:warmup --env=prodAnd this is the exception we get:
"doctrine/doctrine-bundle": "1.6.4",
"doctrine/doctrine-cache-bundle": "1.3.",
"beberlei/DoctrineExtensions": "1.0.",
"doctrine/orm": "2.5.",
"symfony/symfony": "3.1.",
"symfony/framework-bundle": "3.0.*",
If you need more information (config, entities, exception, ...) just tell me.
Thanks in advance,
Stefan
@Ocramius commented on GitHub (Dec 5, 2016):
Entity and related mapping file, please
On 5 Dec 2016 3:24 p.m., "Pointi" notifications@github.com wrote:
@spointecker commented on GitHub (Dec 5, 2016):
Hi, thanks for your really fast response!
Entity:
ORM File:
@Ocramius commented on GitHub (Dec 5, 2016):
Can you re-run the command with a
-vvvflag, to see the exception trace?@spointecker commented on GitHub (Dec 5, 2016):
Sure.
I executed the following command:
(The failing entity changes sometimes, that´s why there is now another entity failing)
bin/console cache:clear --env=prod -vvvOutput:
@Ocramius commented on GitHub (Dec 5, 2016):
Do you by chance extend the entity that you have shown here?
On 5 Dec 2016 3:49 p.m., "Pointi" notifications@github.com wrote:
@spointecker commented on GitHub (Dec 5, 2016):
No the entities aren´t extended at all. Unfortunately this is the most common answer to this problem according to my research. But it´s definitely not the case.
@spointecker commented on GitHub (Dec 5, 2016):
The weird thing is that if I disable all doctrine related deploy commands the deployment works just fine and if I run the commands directly on the instance afterwards it works also just fine.
So if the app has switched from /var/app/ondeck to /var/app/current it works.
I already thought about some permission problems but it (the thrown exception) makes no sense to me.
@spointecker commented on GitHub (Dec 6, 2016):
So I guess you @Ocramius have also no idea left for me? ^^
@Ocramius commented on GitHub (Dec 6, 2016):
@spointecker I don't. I suggest going through with a debugger. Also look for occurrences of those strings (in this case "name") in your project. Also check for listeners attached to the ORM (DoctrineExtensions, for example, may have some)
@Ocramius commented on GitHub (May 20, 2017):
Closing this as not reproducible