The DataNucleus RDBMS mappings are based around ordering of operations for
RDBMS, i.e referential integrity. With GAE/J there are other concerns, namely
knowing the parent before the child, and preventing re-parenting of objects.
Also the backing stores in Datastore (RDBMS) support the full range of storage
(FK, joins, etc including shared FK mappings) and in GAE/J there is currently
only "FK" support for Sets/Lists/arrays. This means that large parts of the DN
backing store code is redundant for this use-case.
There are a significant number of problem areas with GAE/J collection wrappers
- see the issue tracker and forum reports.
Conclusion : rewrite own backing stores suited to what we actually have in
GAE/J.
Original issue reported on code.google.com by googleco...@yahoo.co.uk on 21 Jul 2011 at 2:09
Original issue reported on code.google.com by
googleco...@yahoo.co.uk
on 21 Jul 2011 at 2:09