Support relationships using a field in the owner containing child keys

[GoogleCodeExporter]

When persisting and retrieving we should use the owner field to define the 
relation. v1.0.9+ of the plugin already support storing this information in the 
owner (to an extent). We need to read these fields also. This then makes it 
possible to
1. have multiple relation fields of the same type in a class
2. have unowned relations

Original issue reported on code.google.com by googleco...@yahoo.co.uk on 22 Sep 2011 at 1:50

[GoogleCodeExporter]

SVN trunk could now be safely swapped to StorageVersion 
READ_OWNED_CHILD_KEYS_FROM_PARENTS. Supports all relation types except for 
"ordered lists" which are an illogical concept anyway (due to the fact that it 
throws away the List ordering that the user defined when adding objects to the 
List in Java).

Original comment by googleco...@yahoo.co.uk on 27 Sep 2011 at 3:26

• Changed state: Fixed

[GoogleCodeExporter]

When using SVN trunk with an owned relation, if the property hasn't yet been 
added to the parent record containing the child keys it should fall back to 
using the query of children with that parent (as in v1).

Original comment by a...@datanucleus.org on 31 Oct 2011 at 7:24