Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: 1.0.3
-
Fix Version/s: 1.3-RC1
-
Component/s: Persistence
-
Labels:None
-
Environment:Mac OS X Leopard, Grails 1.0.3
-
Testcase included:yes
Description
Using a many to many relationship with bi-directional navigation fails, if one of the related classes gets subtyped (i.e. subclassed).
For an overview see:
http://siprell.blogspot.com/2008/07/gorm-inheritance-relationships.html
Otherwise I have attached my sources to the Issue. To reproduce run a grails clean and then a grails test-app.
Activity
- All
- Comments
- Work Log
- History
- Activity
- Git Commits
I've cloned this issue highlight the aspect of this bug reported below.
The previous fix (3273) works for most cases, but I've discovered a fringe case: it requires that the class with belongsTo defined has only one belongsTo definition - ie, the following will still produce the error:
i.e. Grails will fail to start with the message:
whereas if the belongsTo is only:
static belongsTo = ShapeIt seems to work as expected.