Jira issue originally created by user saniok:
We have association on non primary key. Something like this:
[-- skipped --]
[-- skipped --]
When I try to fetch Order from Payment with lazy loading I receive empty Order object with null properties. If I use eager fetching Order object is valid.
SQL generated for lazy loading seems to be valid, so I suppose the problem is in mapping result to the object. At the same time lazy loading works fine with 2.0.6 version.
Another problem appears while persisting new Payment.
$payment = new \Entities\Payment();
$order = $this->em->getRepository('\Entities\Order')->find(46320);
I get this error: Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE: Integrity constraint violation: 1048 Column 'scode' cannot be null' in /usr/share/php/Doctrine/DBAL/Statement.php:131
I found issue which is still open and looks like mine -- http://www.doctrine-project.org/jira/browse/[DDC-1114](http://www.doctrine-project.org/jira/browse/DDC-1114). What do you think about this?
Comment created by @beberlei:
Formatting, please add a second ticket for the second issue.
I don't think its supported to use a non primary id for foreign key matching. I cant tell for sure though since i wasnt responsible to design this part of the Doctrine code. I would strongly suggest not to do this.
Marked as improvement. The problem is we cannot detect this invalid mapping, so no exception is thrown during compilation of the mappings,
This kind of mapping error is already acknowledged by the schema-validator console task.
Comment created by saniok:
Should I create second ticket?
Please confirm that I understood correctly. Should we avoid such mapping as it is considered as invalid.
Yes, it will not work at all. You dont need to create the second ticket as that error steams from the mapping error.
You will see an error message when calling ./doctrine orm:schema:validate with this mapping.
Comment created by @deeky666:
This usage is not supported. See: http://www.doctrine-project.org/jira/browse/[DDC-1114](http://www.doctrine-project.org/jira/browse/DDC-1114)
Issue was closed with resolution "Invalid"