You are totally correct, the datastore is extremely tricky to get your head around. I think it is very easy to underestimate the differences between the approaches needed to work with the datastore and more common relational databases.
On Sun, Dec 5, 2010 at 14:42, laboo <mlibu...@gmail.com> wrote: > Yes, I agree, Robert, more documentation isn't always better > documentation. And the point about too much doco leading to much of it > getting outdated is a very good one. > > I still think that GAE, especially the datastore, is very tough for > the average developer to get his/her head around. I think that > Google's strategy is to basically outsource the details of their > documentation to this forum, which is fine, but how effective is it? > I'd love to see numbers on how many developers walk away from GAE > after struggling with it right out of the box. > > Google can certainly afford to hire people to create -- and keep > updated -- top notch documentation. > > On Dec 4, 3:51 pm, Robert Kluin <robert.kl...@gmail.com> wrote: >> Just my personal 2¢: >> >> Overall, I find the App Engine docs pretty decent. There are some >> areas that could use explanation, more details, or clarification, but >> they are not bad. I like the concise to the point nature of them. >> >> I personally hate projects that have massive amounts of obvious / >> useless information in their docs; that almost always leads to very >> outdated / incorrect docs which can be worse than no docs. >> >> RobertOn Sat, Dec 4, 2010 at 18:45, Tim Hoffman <zutes...@gmail.com> wrote: >> > HI >> >> > On Dec 5, 7:24 am, laboo <mlibu...@gmail.com> wrote: >> >> Why doesn't this error message... >> >> >> "Only ancestor queries are allowed inside a transaction." >> >> >> ...look something like this... >> >> >> "Only ancestor queries are allowed inside a transaction. Entity X is >> >> not an ancestor of Entity Y" >> >> > I think you are misreading the error. Its not EntityX is not an >> > ancestor >> > it says you are doing a query, that doesn't have >> > ancestor(some_ancestor) in it. >> >> > A closer look at your code will reveal the problem. >> >> > More docs are nice, but on the whole I don't agree with your laziness >> > sentiments. >> >> > 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 google-appeng...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-appengine+unsubscr...@googlegroups.com. >> > For more options, visit this group >> > athttp://groups.google.com/group/google-appengine?hl=en. > > -- > 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-appeng...@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. > > -- 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-appeng...@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.
