Sort of sucky from a database purist point of view, but you could JSON encode the list (or similar) and put them in a single unindexed text field, which is allowed to be much bigger. Obviously it changes the dynamics of certain operations, but if your typical use is "fetch the entire list" and "put the entire list" (rather than 'search for all lists with a particular ID present' and 'add this one ID to lots of lists') then it may not be an issue, and the CPU requirement to pack and unpack the list as string is unlikely to be that big.
I do this for some small but nested structures where I don't want to split an object across multiple datastore entities - they're fetched and updated as a single unit, and this way I only "pay" for a single db call to get or the put the entire structure of items (and the total string is only about 5k). -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
