This is probably not a good idea. What are your access pattens for this
entity? How many accounts do you usually need to retrieve at once? How
often is an account updated?
If you normally access just a few accounts, then you are incurring the cost
of retrieving all of them every time
I had an idea the other day, but know there's probably some issue I'm
not realizing.
Let's say you have an Account object that represents a registered
user. Instead of having multiple Account objects that you persist to
the datastore, why not have 1 object (ie AccountList) that you
persist, and
