Triple split mapping issue with Doctrine2 - php

Question

I'm encountering a strange problem using Doctrine2.
I'm getting the following error:
doctrine orm:validate-schema
[Mapping] FAIL - The entity-class 'EmailVerification' mapping is invalid:
* The referenced column name 'id' does not have a corresponding field with this
column name on the class 'OurUsers'.
[Database] OK - The database schema is in sync with the mapping files.
My scenario is as follows:
I have 3 tables sharing a primary key.
Table Auth which holds user_id PK.
Table OurUsers for which Auth.user_id is shared PK.
Table EmailVerification for which OurUsers.user_id is shared PK.
I also have NotOurUsers - hence the split.
Entities are declared as follows:
/**
* #Entity
* #Table(name="auth")
*/
class Auth {
/** #Id #Column(type="integer", name="user_id") #GeneratedValue #var int */
private $id;
/* ... */
}
/**
* #Entity
* #Table(name="our_users")
*/
class OurUsers {
/**
* #Id
* #OneToOne(targetEntity="Auth")
* #JoinColumn(nullable=false, name="user_id", referencedColumnName="user_id")
* #var Auth
*/
private $id;
/* ... */
}
/**
* #Entity
* #Table(name="email_verification")
*/
class EmailVerification {
/**
* #Id
* #OneToOne(targetEntity="OurUsers")
* #JoinColumn(nullable=false, name="user_id", referencedColumnName="user_id")
* #var OurUsers
*/
private $id;
/* ... */
}
I'm using Dosctrine 2.1.
btw Doctrine 2.2 validates mappings as good, but I get same error at run time as with 2.1.

Answer 1

I think the problem is that EmailVerfication points to OurUSers intead of to Auth, the error message is misleading though. I am not sure the triple mapping is possible from the internals (i am pretty sure i implemented an exception for this some where as well, i have to look why this is not triggered).

Answer 2

You tell in your JoinColumn statements that you work with a user_id column.
But your column definition for OurUser::id creates a id column by default.
You either have to modify the JoinColumn statement to use id:
/**
* #Entity
* #Table(name="email_verification")
*/
class EmailVerification {
/**
* #Id
* #OneToOne(targetEntity="OurUsers")
* #JoinColumn(nullable=false, name="user_id", referencedColumnName="id")
* #var OurUsers
*/
private $id;
/* ... */
}
OR
add a Column annotation on OurUser::id, like that:
/**
* #Entity
* #Table(name="our_users")
*/
class OurUsers {
/**
* #Id
* #OneToOne(targetEntity="Auth")
* #Column(type="integer", name="user_id")
* #JoinColumn(nullable=false, name="user_id", referencedColumnName="user_id")
* #var Auth
*/
private $id;
/* ... */
}

Answer 3

I think it would be better to switch to something like this, it's a lot more clear and should create less problems:
/**
* #Entity
* #Table(name="auth")
*/
class Auth {
/** #Id #Column(type="integer", name="user_id") #GeneratedValue #var int */
private $id;
/* ... */
}
/**
* #Entity
* #Table(name="our_users")
*/
class OurUsers {
/**
* #Id
* #GeneratedValue
*/
private $id;
/**
* #OneToOne(targetEntity="Auth")
* #var Auth
*/
private $auth;
/* ... */
}
/**
* #Entity
* #Table(name="email_verification")
*/
class EmailVerification {
/**
* #Id
* #GeneratedValue
*/
private $id;
/**
* #OneToOne(targetEntity="OurUsers")
* #var OurUsers
*/
private $ourUser;
/* ... */
}