Added child_enpoints_model example.

[rhodul]

As per #110 (comment) I have added the example for simple parent child relationship.

[dhermes]

Since this is identical to the app config for basic, can you make this a symlink as in

https://github.com/GoogleCloudPlatform/endpoints-proto-datastore/blob/master/examples/basic_with_auth/app.yaml

[dhermes]

@rhodul Thanks for being so thorough! I'm going to check out your branch since viewing an entire new file as a diff is a bit hard on the eyes. A general word of advice, create a new branch before make a pull request so that your master branch can always be a clean copy of the main repo.

[dhermes]

This line (and lines 51 and 53, to name a few) exceed 80 chars, please adhere to PEP8 as close as possible.

[rhodul]

I know, sorry about that. I realized it a bit too late.

On Tue Oct 28 2014 at 4:32:52 PM Danny Hermes notifications@github.com
wrote:

@rhodul https://github.com/rhodul Thanks for being so thorough! I'm
going to check out your branch since viewing an entire new file as a diff
is a bit hard on the eyes. A general word of advice, create a new branch
before make a pull request so that your master branch can always be a clean
copy of the main repo.

Reply to this email directly or view it on GitHub
#112 (comment)
.

[dhermes]

(Moving conversation here to latest diff)

The statement "we do not include it in request body" doesn't clearly indicate why this happens. Instead you could say

  # Unlike in keys_with_ancestors/main.py, we want the datastore to generate
  # child ID, therefore we do not include it in the default message fields schema
  # which determines the request body.

[pfried]

Thank you for this example,maybe i would still trying to find out what is wrong with my code if i had not found it.

Unfortunately the keys with ancestors example uses a string identifier as the id, which is unnecessary to get started. It would be very helpful to have a standard ancestor-child example you can use for getting started and just copy&paste

[dhermes]

@pfried That example is quite complex. The 10 examples are listed on
http://endpoints-proto-datastore.appspot.com/
essentially in order of complexity.

How do imagine you could get ancestor-child in a different way that would be simpler?

[pfried]

@dhermes I would imagine two simple models coupled as parent child by the id property.

The ancestor example http://endpoints-proto-datastore.appspot.com/examples/keys_with_ancestors.html couples them by the parent name, which mixes in another aspect (string field as key). I know most examples cover more than one aspect. But as the ancestor is already very complex i would like to see an example which uses the id property for building the key

[dhermes]

@pfried http://endpoints-proto-datastore.appspot.com/examples/custom_alias_properties.html does just that

[pfried]

@dhermes Sorry, i just took a look at it again (wrote the first comment when i started using the lib) and i realize that it already is the way i asked it to be.

I think i got confused on the if not isinstance(value, basestring): raise TypeError('ID must be a string.') of the Child, because i thought of it as a numerical value

thank you for your patience

[dhermes]

No worries. Glad the library helps you.