On Saturday, May 14, 2011 8:54:54 PM UTC+1, Robert Kluin wrote: > > If the data doesn't get updated, using the blobstore might be a good > idea. As I recall, you can't update a blob. So if the data changes > it may not be the best idea. Of course, it really all depends on the > app / usage.
Ah - never really looked at it that much yet, maybe I'll save the blobstore for when I go back to pure functional code and immutable data structures again :) > I store serialized dicts / lists in text / blob properties quite > often. It works well for me. > Yep, that might be they way to go - I never need to search by the internal fields, and whereas for SQL the idea of partial updates works well, in the datastore you always pull back the whole object and re-save the whole object even if it's just a single field/property being updated. Feels somewhat unclean not to follow the usual discipline of at least partially abstracting the data model at the back end, but I only use the datastore as a blind repository anyway. Cheers -- T -- 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.
