ResultSetMappingBuilder and name conflict in mapper
up vote
1
down vote
favorite
I've got entity A with two ManyToOne relations. And both join columns with same name. When I am creating query based on entity A with ResultSetMappingBuilder and setting this entity to method addRootEntityFromClassMetada it results in InvalidArgumentException The column 'created_by' conflicts with another column in the mapper..
Here is quick sample for entity A
/**
* @var B
* @ManyToOne(targetEntity="B")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $a;
/**
* @var C
* @ManyToOne(targetEntity="C")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $b;
How can I avoid to conflict? I tried almost everything that I found on stack. But there are not many problems with this.
Doctrine 2.6.1
Thanks for you answers,
Michal
php doctrine2 doctrine
asked yesterday
Michal Hlávka
463
add a comment |
up vote
1
down vote
favorite
I've got entity A with two ManyToOne relations. And both join columns with same name. When I am creating query based on entity A with ResultSetMappingBuilder and setting this entity to method addRootEntityFromClassMetada it results in InvalidArgumentException The column 'created_by' conflicts with another column in the mapper..
Here is quick sample for entity A
/**
* @var B
* @ManyToOne(targetEntity="B")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $a;
/**
* @var C
* @ManyToOne(targetEntity="C")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $b;
How can I avoid to conflict? I tried almost everything that I found on stack. But there are not many problems with this.
Doctrine 2.6.1
Thanks for you answers,
Michal
php doctrine2 doctrine
asked yesterday
Michal Hlávka
463
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I've got entity A with two ManyToOne relations. And both join columns with same name. When I am creating query based on entity A with ResultSetMappingBuilder and setting this entity to method addRootEntityFromClassMetada it results in InvalidArgumentException The column 'created_by' conflicts with another column in the mapper..
Here is quick sample for entity A
/**
* @var B
* @ManyToOne(targetEntity="B")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $a;
/**
* @var C
* @ManyToOne(targetEntity="C")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $b;
How can I avoid to conflict? I tried almost everything that I found on stack. But there are not many problems with this.
Doctrine 2.6.1
Thanks for you answers,
Michal
php doctrine2 doctrine
asked yesterday
Michal Hlávka
463
I've got entity A with two ManyToOne relations. And both join columns with same name. When I am creating query based on entity A with ResultSetMappingBuilder and setting this entity to method addRootEntityFromClassMetada it results in InvalidArgumentException The column 'created_by' conflicts with another column in the mapper..
Here is quick sample for entity A
/**
* @var B
* @ManyToOne(targetEntity="B")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $a;
/**
* @var C
* @ManyToOne(targetEntity="C")
* @JoinColumn(name="created_by", referencedColumnName="id")
*/
private $b;
How can I avoid to conflict? I tried almost everything that I found on stack. But there are not many problems with this.
Doctrine 2.6.1
Thanks for you answers,
Michal
php doctrine2 doctrine
php doctrine2 doctrine
asked yesterday
Michal Hlávka
463
asked yesterday
Michal Hlávka
463
asked yesterday
Michal Hlávka
463
asked yesterday
Michal Hlávka
463
asked yesterday
Michal Hlávka
463
463
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday
add a comment |
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371302%2fresultsetmappingbuilder-and-name-conflict-in-mapper%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Sadly I no longer have access to code where I've faced the issue but I think I worked this around aliasing conflicting columns. There's also a chance I had to manually map RSM due to this.
– malarzm
yesterday