GPMONGODB-92: Associations in an embedded instance should not be forcibly embedded as well #158
Description
Original Reporter: emedina
Environment: Not Specified
Version: 1.0.0.M7
Migrated From: http://jira.grails.org/browse/GPMONGODB-92
I have a class A which defines a field b of type B (not embedded, no has* definition). Then, in class C I define a field a of type A and I set it as embedded.
When an instance of class C is saved with 1.0.0.M7, field b in embedded field a is also embedded, and it should not, IMHO; I should be able to define whether field b in class A must also be embedded or just treated as a normal association, i.e. stored as a DBRef.
See MongoDB output ("b" in "a" should not have been embedded):
db.b.find()
{ "_id" : ObjectId("4e518e93b28efcd4e07b8b57"), "name" : "Name1", "version" : 0 }
db.c.find()
{ "_id" : NumberLong(1), "a" : { "b" : { "name" : "Name1", "version" : NumberLong(0) } }, "version" : 0 }