Creating a database per team is a very heavyweight way to address the
problem of data segregation. This is unnecessary and in general, not a
recommended best practice, as you would provide data isolation at the
application layer. The intuitive solution here is to create an entity group
for a league
Yes App Instance <=> Datastore Instance is a one to one mapping.
As for maintaining domain separation see
http://blog.notdot.net/2009/11/API-call-hooks-for-fun-and-profit
2009/12/1 andreas_b :
> Hi all.
>
> I'm working on a GWT/GAE project where the idea is to create a portal
> for sport teams.
Hi all.
I'm working on a GWT/GAE project where the idea is to create a portal
for sport teams. Each sport team can sign up to get an account where
they can register players, keep track of leagues, matches, statistics
and so on. Each team should also be able to use their own domain,
which automatic
