1

If you could wave the magic wand and fix something in the GAE 1.5.5 documentation that have caused you lost time, grief, or missed opportunities, what would they be?

Dave W. Smith
  • 24,318
  • 4
  • 40
  • 46
  • 1
    I think this topic is interesting, but not a good stackoverflow question. There is no "right answer" to this question. At the very least it should be a community wiki. – Peter Recore Oct 19 '11 at 16:38
  • 1
    Also, "one thing" would be a better question than "three things" - that way people can vote up individual answers. @PeterRecore CW doesn't really exist anymore. – Nick Johnson Oct 20 '11 at 03:18
  • Reworded. The context for the question is a chance to move workarounds upstream, into the docs. – Dave W. Smith Oct 20 '11 at 18:53
  • So one thing that I didn't know about for a long time, until Nick mentioned it in a solution, was the ability to use path components as parameters. It seems like a pretty important piece of functionality and I still can't seem find it in the webapp documentation. – Kevin P Oct 20 '11 at 22:43
  • I find it an interesting and useful question; thanks for asking! – systempuntoout Oct 21 '11 at 06:58
  • @Dave hey Dave, thank to have marked my answer as accepted but..what does it mean? Are you going to fill the gap of the documentation :)? – systempuntoout Nov 04 '11 at 21:52
  • The gnomes have been busy filling gaps. – Dave W. Smith Nov 06 '11 at 02:07

1 Answers1

4

Now that the Datastore reads is a crucial quota in our billing, I would like to read something about the "Datastore reads costs" since only the write part is covered.

Community
  • 1
  • 1
systempuntoout
  • 71,966
  • 47
  • 171
  • 241