Details
Description
Mapper
<entity name="Default_Model_Test" table="test"> <id name="id" type="integer" column="id"> <generator strategy="AUTO"/> </id> <field name="blabla" column="blabla" type="boolean"/> <one-to-one field="user" target-entity="Users_Model_User"> <join-column name="users_id" referenced-column-name="id" on-delete="CASCADE" on-update="CASCADE" unique="false" /> </one-to-one> </entity>
SQL
CREATE TABLE test (id INT AUTO_INCREMENT NOT NULL, users_id INT DEFAULT NULL, blabla TINYINT(1) NOT NULL, UNIQUE INDEX test_users_id_uniq (users_id), PRIMARY KEY(id)) ENGINE = InnoDB; ALTER TABLE test ADD FOREIGN KEY (users_id) REFERENCES users(id) ON UPDATE CASCADE ON DELETE CASCADE;
Actual:
UNIQUE INDEX test_users_id_uniq (users_id)
Expected:
INDEX test_users_id (users_id)
Verified, i just don't understand why you are using a one-to-one relation and then "deactivate" the database constraint for this. You could easily use Many-To-One