The biggest question is why would you want to do this?
From the low-level api perspective, you can't have a list property with
more than 5k items. But maybe JDO models this list as a proxy to a query.
When you try to load that proxy it's going to load all 5m items out of the
datastore and you
Forget about this way : even if this having millions of children
entities for one ancestor is theoretically feasible, you'll hit a
write performance issue when you generate those entities : only 1
write / second in one given entity group (ancestor).
On 17 fév, 03:16, hendrix.jason
