[google-appengine] Re: Architectural advice needed: background report generation

Thank you, most helpful! On Saturday, June 10, 2017 at 11:01:52 AM UTC+2, Karoly Kantor wrote: > > I have a rather complex data base structure on which I need to enable > users to define various reports and run them in the background. (As the > generation time might exceed what is acceptable

Re: [google-appengine] Architectural advice needed: background report generation

On Sat, Jun 10, 2017 at 2:01 AM, Karoly Kantor wrote: > I have a rather complex data base structure on which I need to enable > users to define various reports and run them in the background. (As the > generation time might exceed what is acceptable real-time.) I want to >

[google-appengine] Entity data change

Hi anyone please update me that, If due to my client requirement if I got changes to entity then previous data gets invalid what is the correct approach please. I mean that if one of the attribute of my entity is searialize and after client communication if that attributes

[google-appengine] Re: Cloud Datastore tutorial fails with exception

Awesome. That's great to hear, Yannick. On Friday, June 9, 2017 at 1:32:42 PM UTC-7, Yannick (Cloud Platform Support) wrote: > > Hello Jay-Nicolas, thank you very much for the detailed answer. I did > manage to replicate your issue when using the local dev server on a Windows > 10 VM. The code

[google-appengine] Architectural advice needed: background report generation

I have a rather complex data base structure on which I need to enable users to define various reports and run them in the background. (As the generation time might exceed what is acceptable real-time.) I want to enable users to launch the generation of these reports and then get a notification

Re: [google-appengine] Transaction usage

This is sort of a fundamental database question that isn’t directly related to Objectify or the datastore, but I’ll have at it: If you want a series of operations to occur as if they are executed in serial, you need to use transactions and you need *each* operation to be wrapped in a transaction.

Re: [google-appengine] Best Practices for Search API?

No not at all; quite the opposite, really. I was storing word fragments for typeahead, eg “foobar” became [“f”, “fo”, “foo”, “foob”, “fooba”, “foobar”]. It was very expensive to index in the datastore and very cheap to index in the search api. The search API is pretty cool. I hope Google makes an