Issue/17 consistency

changed the models for strong consistency, which means every entity has a direct parent, except for two root models (User and Club)

_implication_: the resources should be adressed with the whole ancestor path (i.e. /trainers/1/clients/2/phases/3/circuit/4/exercises/5, or /clubs/1/trainers/)

transfered the models to use the NDB api from google-appengine instead of DB (always stay cutting edge!)

also added some documentation for the API (with examples)
Okay, I guess that's fine. I believe the system would automatically clear
the trainer from the user lists if it was deleted but in either case
there's some extra work for changing clubs.
On 21 Dec 2014 17:39, "Damien Firmenich" <notifications@github.com> wrote:

> In api/rest/trainer.py
> <https://github.com/damienfir/fitmap/pull/19#discussion-diff-22148643>:
>
> >
> > -    _parent = Club
> > +    _parent = api.core.user.User
>
> Indeed, the trainer wouldn't take his clients so in both case we have to
> update all the clients' trainer set. But I'd rather change a single club
> reference instead of cloning a trainer's entity (and all it's exercise
> library).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/damienfir/fitmap/pull/19/files#r22148643>.
>