One thing to consider is that if you are never searching on the integers themselves, then keeping them out of indexed properties should reduce some overhead in creating/updating indexes (which automatically exist for all Integer and List fields!). So if you went with your hourly entity approach, you could keep the data itself in a Blob of Text property (neither of which is automatically indexed).
On Jan 31, 4:30 am, Adi <[email protected]> wrote: > The app I'm currently working on would have to store for every user a > few (3-4) integers for every minute of the day. > Should I store each minute for a user as an entity in the datastore, > or would this be too much overhead? > Perhaps another solution would be to store a list for every hour, the > list having 60 elements (or maybe a pickled dictionary?), one for each > minute. When querying for a certain minute, I can just query the hour > and get the required element from the list. > What approach would you recommend?. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
