How about keeping each entity in the DB, and keep a 2D array of their IDs? Use memcache to keep the 2D array handy (with lazy sync to the data store).
On Dec 26, 2011, at 2:08 PM, Chuck Lega wrote: > I want to store a dynamic ~100x100 array of "SimpleEntity":s > (containing just a few primitives) which I need to access in lots of > ways... read/write single items, get complete rows, get complete > columns, add and delete columns and rows and more. I dont want sparse > arrays. > Now, what would be the best way of doing this. I have experimented > with having each cell be its own entity, but it ends up really messy > to keep the grid consistent, with adding/removing rows for example. > Now I am about to give up, thinking to just go with a blob of > SimpleEntity[][] and serialize/deserialize for each access... It feels > kinda wrong(?), but it keeps things simple(?). > What would be the proper way of doing this? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
