You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by "Thomas Dudziak (JIRA)" <ji...@apache.org> on 2005/08/20 21:58:58 UTC
[jira] Resolved: (OJB-67) Add a new check to the xdoclet module to avoid weird mapping errors of one-to-many relationships
[ http://issues.apache.org/jira/browse/OJB-67?page=all ]
Thomas Dudziak resolved OJB-67:
-------------------------------
Resolution: Fixed
I've added two warnings: use of remote-foreignkey for 1:n collections, and foreignkey = remote-foreignkey for m:n collections
> 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, 1.1 CVS
> Environment: OJB 1.0.3
> Reporter: Guillaume Laforge
> Assignee: Thomas Dudziak
> Fix For: 1.0.x CVS, 1.1 CVS
>
> 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: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org