Add a new check to the xdoclet module to avoid weird mapping errors of
one-to-many relationships
------------------------------------------------------------------------------------------------
Key: OJB-67
URL: http://issues.apache.org/jira/browse/OJB-67
Project: OJB
Type: Improvement
Versions: 1.0.3
Environment: OJB 1.0.3
Reporter: Guillaume Laforge
I had a weird transaction problem, where I couldn't manage to store a
one-to-many relationship within a transaction.
This was quite misleading, because in fact, that was just a mapping problem.
I mistakenly used both foreignkey and remote-foreignkey pointing at the same
column, though the remote-foreignkey wasn't needed since that was a one-to-many
relationship and not a many-to-many relationship.
So the idea would be to add a sanity check to verify that you can't have both
foreignkey and remote-foreignkey attributes pointing at the same column.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
